Prior to SQL Server 2008, SQL developers were restricted to using two types to work with date and time values: datetime and smalldatetime. While they are sufficient in most user scenarios, there are some limitations: 1) Both types include both the date value and time value. There is no way to store only the date …
Continue reading “SQLClient Support for the New Date and Time Types in SQL Server 2008”
Here’s a list of things to know if you’d like achieve the best performance/scalability with SqlClient: Use SqlBulkCopy to send large sets of data to the server Set DbDataAdapter.UpdateBatchSize to send batches to the server Use strongly typed getters instead of GetValue/GetSqlValue Turn on CommandBehavior.SequentialAccess and call GetChars/GetBytes when working with BLOBs Use parameterized queries …
Background Consider the following two scenarios: 1. You have implemented a .NET application accessing a specific COM+ service with automatic transaction processing. You derived a class from ServicedComponent, set the Transaction attribute for the class, and applied the Automatic attribute to a method which opens a SqlConnection. 2. Inside a TransactionScope, you wanted to open …
Continue reading “Using MSDTC between Vista clients and Windows 2000 servers”
Under some circumstances (such as with certain network bandwidth), you might get a general network error in .Net Framework 1.1 when executing a query that takes longer than SqlCommand.CommandTimeout value. This has something to do with how SqlClient 1.1 deals with timeout. Basically we track the timeout value by decrementing it each time after we …
Continue reading “General Network Error in .Net Framework 1.1”
http://support.microsoft.com/kb/913764/ The KB article didn’t say a lot of details about this bug. Usually the following conditions have to been met in order to trigger the bug: 1. Query must run against sql2000 (Sql2005 works fine) 2. The table name has to include 3 or more dots, ie: [A.B.C.D.E] 3. There has to be an …
There was a bug in SqlClient which could cause high CPU use. The scenario is a SqlClient application sends an attention to Sql Server but receives no acknowledgement from the server because the connection is broken. The bug lies in the logic of reading server’s response from the wire. We buffer the incoming data from the wire. …
For certain size of data, SqlBulkCopy.WriteToServer() may throw a timeout exception, although it won’t happen when MARS is turned on. The problem is caused by a bug in the code for handling some boundary scenarios. The workaround is to apply this patch: http://support.microsoft.com/kb/913177/
Exception Type: System.Data.SqlClient.SqlException Number: 3988 Message: New transaction is not allowed because there are other threads running in the session If you have ever seen this type of exception when talking to RTM SQL Server 2005 (but never saw it with the Beta version of the server), it’s likely that you have an open data …
There’re a lot of resources online talking about ADO.NET: 1. Data Access and Storage Developer Center: official Data website at microsoft.com. 2. Data Access Blog: team’s blog site. You may find information interesting from different team members. 3. .NET Framework Data Access and Storage – MSDN Forums: it’s a place where lots of developers are …