Normally an ADO .NET connection string uses “server” or “data source” to specify the machine name \ sql server instance, your application will be connecting to.

data source = .\sql instance name
server = .\sql instance name


SqlConnection conn = newSqlConnection(@”data source = .\sql2012;
                                         integrated security = true;
                                         database = AdventureWorks”);

But there are few more ways to specify the same

address = .\ sql instance name
addr = .\ sql instance name
network address = .\ sql instance name

SQL Server 2008 and SQL Server 2012 are two separate versions of databases.

Also, SSMS (SQL Server Management Studio) of SQL Server 2008 and SQL Server 2012 have different look and feel (UI).

But, SQL Server 2008 SSMS can still successfully access and connect to SQL Server 2012 instance.
Similarly, SQL Server 2012 can connect to SQL Server 2008 instance.

SSPI stands for Security Support Provider Interface. The SSPI allows an application to use any of the available security packages on a system without changing the interface to use security services. The SSPI does not establish logon credentials because that is generally a privileged operation handled by the operating system.

Usually a .NETconnection string looks like this, you will have your own server, databse names ofcourse.

“Data Source=localhost\sql2012;Initial Catalog=AdventureWorks;
Integrated Security=SSPI”

Other than SSPI you can also use “true”. Integrated Security actually ensures that you are connecting with SQL Server using Windows Authentication, not SQL Authentication; which requires username and password to be provided with the connecting string.


If you are looking for Web Service project template in Visual Studio 2010 under .NET Framework 4.0 as shown in the image below, you will not find it.

In order to create a WebService using Visual Studio 2010 you need to switch back to .NET Framework 3.5, as shown in the image below, and you will be able to crate a WebServeice project.

In order to connect with SQL Azure Db, you need special version of SQL Server Management Studio.

Ability to connect with SQL Azure is buid in “SQL Server 2008 R2 November CTP”.

You can download this from SQL Server® 2008 R2 November Community Technology Preview – Express

How many times you encountered a situation when you need to change the screen resolution or text size to make you code to appear in larger font. I encountered couple of time and instances especially when disusing something with team and people sitting far can’t see the code statements at all, in presentations etc.

The solution has been an easy approach, change resolution or change the font size from Tools –> Options. What appeared tedious to me was re-setting either one of these after the purpose is over.

VS 2010 Code Editor comes up with this new feature where you can just simply ZOOM your entire code editor view without changing resolution or text size.
To do so it’s a well known trick “Hold Left-click and scroll the Mouse Wheel.”


Click on the image to see larger view and use browser’s back button to re-visit this post.

VS2010 IDE provides a new menu named Data and it has a brand new feature item “Transact-SQL Editor” this feature allows you to perform the db operations without leaving the VS development environment.
* Microsoft’s another step forward to make it a real IDE (Integrated Development Environment).

Read more about this feature on previous post:

SQL 2008 is the main candidate which gets the privilege to provide db service to this new Data menu of VS2010, and so SQL 2008 express is part of VS2010 installation. Whereas this new Transact-SQL Editor is capable enough to connect to SQL 2005 instance as well. When it prompts for connection, by default it pulls SQL 2008 instance name (SQLExpress), you can choose “Browse for more” option and then expand the “Database Engine” node and select the SQL 2005 instance.

Now you are good to go and do your db work with SQL Server 2005 from VS 2010 IDE.

Microsoft will be providing an ability to upgrade exiting VS2008 environment into VS2010.

Whereas, it is also possible to have various VS (2005, 2008 and 2010) installtions to be available and run on the same machine.

For VS 2010 Beta users, Microsoft is also providing an upgrade path to be upgraded into VS 2010 final vesrion rather than doing a fresh and clean install.