|
|
|
|
|
|
SQL Server 2008 : General T-SQL Performance Recommendations |
How you write T-SQL queries can often have an effect on the performance of those queries. The following sections provide some general guidelines to keep in mind to help ensure that you are getting optimal performance from your queries. |
|
|
|
|
|
|
|
SQL Server 2008 : Using Remote Stored Procedures |
The processing done by the remote stored procedure is, by default, not done in the local transaction context. If the local transaction rolls back, modifications performed by the remote stored procedure are not undone. |
|
SQL Server 2008 : Using Temporary Tables in Stored Procedures |
Temporary tables are commonly used in stored procedures when intermediate results need to be stored in a work table for additional processing. Local temporary tables created in a stored procedure are automatically dropped when the stored procedure exits |
|
|
|
|
|
SQL Server 2008 : Using ADO.NET Data Services |
ADO.NET Data Services (ADODS) is a platform for providing SQL Server data to websites, RIAs (such as Silverlight and Flash applications), and other Internet clients over standard HTTP using modern web development conventions. |
|
|
SQL Server 2008 : Developing with LINQ to SQL (part 1) |
LINQ enables developers to write code in either C# or VB.NET using the same set of syntactic conventions to query object collections (known as LINQ to Objects), XML documents (known as LINQ to XML), SQL Server data (known as LINQ to SQL), and other queryable resources. |
|
Getting Comfortable with ADO.NET 3.5 and SQL Server 2008 |
To start coding with ADO.NET and SQL Server, you first need to connect to an instance of SQL Server. To do this, you need a connection string. A connection string is simply a string literal that contains all the parameters necessary to locate and log in to a server in a semicolon-delimited format |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|