You want to speed up data access in an application that will always be used with SQL Server.
Use the SQL Server managed provider instead of the
OleDB managed provider for accessing the data in the database.
In the code-behind class for the page, open a connection to a SQL Server database using the
SQLConnection class and then use the SqlCommand, SqlDataReader, and SqlDataAdapter objects as required by your application.
To test the SQL provider, we have implemented our example from Recipe 19.3 and replaced the
getDataAdapterTime methods in the code-behind with the code shown in Examples 19-10 (VB) and 19-11 (C#). The output of the test is shown in Figure 19-3.
Figure 19-3. Performance using SQL managed provider output
The CLR provides four managed providers for accessing data in a database: SQL,
OleDB, ODBC, and Oracle. The
OleDB and ODBC providers can be used to access virtually any database—including SQL Server, Access, Oracle, and many others—using an
OleDB (or ODBC) layer.
OleDB communicates to a data source through the
OleDB service component, which provides connection pooling and transaction services, and the
OleDB provider for the data source. In contrast, the SQL Server provider uses a proprietary protocol to access SQL Server directly, eliminating the additional ...