Figure 4: SQL Server-to-client data flow, client data using a code page, SQL Server using Unicode data types In figures 5 and 6, the client data is in Unicode, and SQL Server is not. Figure 5: Client-to-SQL Server data flow, client using Unicode, SQL Server using a code page Figure 6: SQL Server-to-client to data flow, client using Unicode, SQL Server using a code page Collations in SQL Server 2008 New in SQL Server 2008 What’s Figure 7 illustrates the collation additions in SQL Server 2000, SQL Server 2005, and SQL Server 2008. Figure 7: Collations in SQL Server Earlier Versions of the Native Data Provider Collations Not Recognized by Earlier Versions of the Native Data Provider Of the new Windows collations introduced in SQL Server 2008, the collations listed in figure 7 in black bold italic type are not recognized by earlier versions of the native data provider during connection to a SQL Server 2008 database if both the client and the server environment are not in Unicode. There are several possible result cases; for example, consider the following scenario. This can happen with Windows Server 2003 and earlier, as stated previously. It can also Note: happen with Windows Server 2008 and Windows Server 2008 R2. For instance, consider a situation in which SQL Server 2005 and SQL Server 2008 are installed side-by-side on Windows Server 2008. A SQL Server 2005 data provider, such as Microsoft SQL Server Native Client 9.0 (SNAC9) or Windows Data Access Components (Windows DAC), is used to connect to an instance of SQL Server 2008 that uses one of the new unsupported SQL Server 2008 collations.
Figure 4: SQL Server-to-client data flow, client data using a code page, SQL Server using Unicode data types In figures 5 and 6, the client data is in Unicode, and SQL Server is not. Figure 5: Client-to-SQL Server data flow, client using Unicode, SQL Server using a code page Figure 6: SQL Server-to-client to data flow, client using Unicode, SQL Server using a code page Collations in SQL Server 2008 What’s New in SQL Server 2008 Figure 7 illustrates the collation additions in SQL Server 2000, SQL Server 2005, and SQL Server 2008. Figure 7: Collations in SQL Server Earlier Versions of the Native Data Provider Collations Not Recognized by Earlier Versions of the Native Data Provider Of the new Windows collations introduced in SQL Server 2008, the collations listed in figure 7 in black bold italic type are not recognized by earlier versions of the native data provider during connection to a SQL Server 2008 database if both the client and the server environment are not in Unicode. There are several possible result cases; for example, consider the following scenario. Note: This can happen with Windows Server 2003 and earlier, as stated previously. It can also happen with Windows Server 2008 and Windows Server 2008 R2. For instance, consider a situation in which SQL Server 2005 and SQL Server 2008 are installed side-by-side on Windows Server 2008. A SQL Server 2005 data provider, such as Microsoft SQL Server Native Client 9.0 (SNAC9) or Windows Data Access Components (Windows DAC), is used to connect to an instance of SQL Server 2008 that uses one of the new unsupported SQL Server 2008 collations.
Pre-SQLServer2008_NativeDataProviders_and_NewCollations.docx