Skip to main content

SQL Server Connection Strings

The purpose of this short post is to demonstrate a simple method of generating an accurate SQL Server connection string for your SQL Server servers and databases.  This tip was first showed to me by a friend of mine, Paul Blackwell, a while back and I wanted to share it with you here.

As pre-requisite to this tip you need to be using a windows based operating system.

In order to build our SQL Server connection string we need to clear all open windows and have the desktop in front of us…

so click the <show desktop> button

<Right click> on the desk top

Select <New> <Text Document>


Call it <sqlconn>

Open the new text document called <sqlconn>on your desktop

When the document is open select <File><Save As>

Keep the file name the same but change the <save as type> to all files.

After the file name add the extension .udl like in the screen shot below and click <Save>


There will now be a second item on the desktop called <sqlconn> and will look similar to this (depending on your version of windows)


Double click on the icon will take you a data link connection page like the following.

Select the <Provider> tab and select <Microsoft OLE DB Provider for SQL Server> click <Next>


On the <Connection> tab enter the details of the server you want to connect to including any connection details. I always like test the connection too


Click <OK>

The will take you back to the desktop…

The final step to get the code for your SQL Server Connection string…

<Right Click > on the .UDL file <sqlconn>
Select <open with> and choose notepad
And the file that opens should contain the following code:

; Everything after this line is an OLE DB initstring
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=RBBS;Data Source=localhost

You can you use this method to create a number of connection strings, in this tip we have looked at generating code for SQL Server connection string but it can also be used for host of other connection strings including Analysis Services and SSAS.


Popular posts from this blog

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

New in SQL Server 2017: Graph Databases

David has recorded and published a video of his presentation on SQL Server Graph Database. In his video which you can watch below, David provides an excellent introduction into SQL Server 2017 Graph Databases. In his presentation he looks at Tennis results at tournaments for  his favourite player "The Fed"  Rodger Federer.

David  shows how to set up graph database and work with them in SQL Server 2017.

Graph Database is not new. Other vendors have had graph database capabilities for some time so Microsoft are quite late to the market. In David presentation it appears that Microsoft have done a reasonable job of implementing some of the graph database features but he does point some of the limitations of the Microsoft product too and suggests that it is not ready for production yet but Microsoft seem serious about this feature.

Please watch the video and feel free to leave a comment or feedback - David is delivering a version of this talk on Graph databases in SQL Saturday Ka…