Faster access to SQL Server using the SqlClient data library

-

.Net supports data access through ADO.Net which provides a generic mechanism to access data. Unlike previous versions of data connector technology Microsoft decided to break with tradition and provide a customized library for SQL Server meant to improve performance by bypassing the high level OleDb API to access the database engine. The SqlClient namespace provides access to the SQL Server specific versions of objects for connecting and accessing the database while the OleDb namespace houses the same functionality for the generic OleDb driver access. You can use either for accessing SQL Server, but the SqlClient objects will be somewhat faster and specifically tuned for SQL Server.

In practice this means if you want to use the Sql Server specific classes you will need to bracket your code if you also want to support other data sources because the object names vary for each of the class libraries. All Sql Server objects start with Sql like SqlConnection, SqlCommand and SqlDataAdapter, while the OleDb versions start with OleDb.

The interfaces for the driver objects is open and extendable through .Net so you can expect to see other database vendors to build .Net classes that are optimized for their data engines. In fact building a new provider is relatively painless and involves override and implementing a handful of methods in the various data access classes (Connection, DataAdapter, Command), so it's possible to use straight .Net code to create a provider with much less effort than previously required through the OleDb interfaces.

Comments

Post a Comment

Popular posts from this blog

ASP.NET Compillation Error BC31007 - Solution

-
TToday while I am working on the ASP.NET application, I suddenly encountered with below error while trying to debug the application. I tried couple of actions: .    ·           Clean and rebuild solution ·          IDE restart ·          Temporary asp.net files cleanup ·          System restart ·          Modified Identity in App pool Finally it got resolved by modifying the Identity to “Local System” in Application Pool Server Error in '/My App’ Application. Compilation Error Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately. Compiler Error Message: BC31007 : Unable to open module file 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\crs\b1234521\35244951\App_global.asax.v8-jml4w.0.vb': System Error &Hc0000005& (Visual Basic internal compiler error) Source Error:
Read more

The Difference between GET and POST

-
When the user enters information in a form and clicks Submit , there are two ways the information can be sent from the browser to the server: in the URL, or within the body of the HTTP request. The GET method, which was used in the example earlier, appends name/value pairs to the URL. Unfortunately, the length of a URL is limited, so this method only works if there are only a few parameters. The URL could be truncated if the form uses a large number of parameters, or if the parameters contain large amounts of data. Also, parameters passed on the URL are visible in the address field of the browsernot the best place for a password to be displayed. The alternative to the GET method is the POST method. This method packages the name/value pairs inside the body of the HTTP request, which makes for a cleaner URL and imposes no size limitations on the forms output. It is also more secure. ASP makes it simple to retrieve name/value pairs. If the forms output is passed after the question mark (?
Read more

Test & Debug WCF service using WCFTestClient.exe

-
Image
VS.NET 2010 provides WCFTestClient.exe for us to test and debug the WCF service.  Please follow me to test and debug the service. Generally, first debug and then test the service, but here first I will tell you how to test it and then how to debug it J Test the WCF service using WCFTestClient. 1.        Open “Visual Studio Command Prompt (2010)” 2.        Go to “c:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\” 3.        Run WcfTestClient.exe 4.        It will open WCF Test Client, now add WCF Service (URL) 5.        Select the service method, from left panel 6.        Provide request data (i.e. values to parameters) on right panel and click on Invoke button. It gives you the response. Debug the WCF service, follow the commands. 1.        Go to WCF service project properties 2.        Go to Web menu on left menu 3.        Select WcfTestClient.exe from “c:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\” for “Start external progr
Read more