New Features in SQL Server 2008 (ADO.NET)
SQL Server 2008 introduces new features and enhancements designed to increase the power and productivity of developers, architects, and administrators. Improvements include new Transact-SQL statements, data types, and management features. For the complete list of new features, see What's New (SQL Server 2008) in SQL Server 2008 Books Online. For Database Engine features, such as new Transact-SQL statements, management tools, and security enhancements, see What's New (Database Engine) in SQL Server 2008 Books Online.
SQL Server 2008 R2 is an incremental release to SQL Server 2008, introducing enhanced features and functionality such as support for more than 64 logical processors, application and multi-server management features, Master Data Services (MDS), as well as improvements to Reporting Services. For a complete list of new features, see What's New in SQL Server 2008 R2 in SQL Server Books Online. Starting with the .NET Framework 4, the .NET Framework Data Provider for SQL Server (System.Data.SqlClient) provides full support for all the new features of the SQL Server 2008 Database Engine.
Starting with the .NET Framework version 3.5 Service Pack (SP) 1, the .NET Framework Data Provider for SQL Server (System.Data.SqlClient) provides full support for all the new features of the SQL Server 2008 Database Engine. You must install the .NET Framework 3.5 SP1 (or later) to use these new features with SqlClient.
The following topics are located in the ADO.NET documentation.
The functionality available to a client application is dependent on the version of SQL Server and the compatibility level of the database. The Type System Version keywords in a SqlConnection::ConnectionString can be used to specify the client-side representation of SQL Server types. Explicitly setting the type system version that the client application was written for avoids potential problems that could cause an application to break if a different version of SQL Server is used. For example, UDT columns are represented as a byte[] array if you specify SQL Server 2000. If you specify SQL Server 2005, they are represented as managed types.
The available Type System Version values are described in the following table.
Value | Description |
|---|---|
Latest | Uses the latest version that this client-server pair can handle. The version used will automatically move forward as the client and server components are upgraded. This is the default setting in ADO.NET. |
SQL Server 2000 | Uses the SQL Server 2000 type system. |
SQL Server 2005 | Uses the SQL Server 2005 type system. |
SQL Server 2008 | Uses the SQL Server 2008 type system. Datetime values are processed based on the type system version and the default language specified on the server. |
For compatibility with features introduced in SQL Server 2008, you can explicitly supply the Type System Version in the connection string by using one of the following.
Type System Version= SQL Server 2008; Type System Version=Latest;
Note |
|---|
The type system version cannot be set for common language runtime (CLR) code executing in-process in SQL Server. For more information, see SQL Server Common Language Runtime Integration (ADO.NET). |
You can also set the TypeSystemVersion property of a SqlConnectionStringBuilder when creating connection strings at run time. For more information, see Connection String Builders (ADO.NET).
Note