A good way to start a day. Just got an email regarding another latest addition to my cert list. Microsoft Certified Technology Specialist : .NET Framework 3.5 ADO.NET Applications More...
Here's an interesting I came across in the recent Simple Talk Newsletter (by Red Gate Software).
It talks about issues with new SQL 2008 data types (date/time related) and it's effect on .NET 2.0 datetime data types when SP1 is installed or not. Something to be aware of and one of those times that you're glad you have a web rather than a desktop application. (you only have to install SP1 on the server(s))
SQL Server 2008 has introduced a few new data types, among others the
new date types, like date, time, datatime2 and datetimespan. Because
.Net 2 was released before SQL Server 2008 has introduced these data
types, there are no classes that map to these new types in .Net 2.
But this has changed with .Net 2 SP1, which introduces the DateTimeOffset structure.
Read full article from the following link :SQL Server 2008: new data types and .Net 2 with and without SP1
If you perform multiple select queries inside your stored procedures I believe you actually return all of the result sets to the client. (except when you assign a value to a parameter like SELECT @myVar = [ColumnA] FROM Table1). This is something to be careful of since you might unnecessarily return results sets that you actually don't need to return.
But this behavior also has an advantage. Obviously, if you need to retrieve two result sets, there is no need to create two or more SqlCommand to retrieve them. I believe this is handled under the hood if you use SqlDataAdapter.Fill where the dataset being filled will result the sets as part of its tables collection. However in this example we will illustrate how it can be done using SqlDataReader using non other than Reader.NextResult() method.
This is something I don't see often (might not be the case for you) so without much further ado, here's a sample code that might explain better than words. More...
Quoting from the SQL Programmability and API Development Team Blog: Multiple Active Result Set or MARS is defined as
a new programming interface introduced in SQL Server 2005. It
enables multiple result sets to exist at the same time for a given
connection. To say it in a simple way, you can make a connection to
server and then submit multiple requests to serve
To illustrate, More...