Chapter 18 – Getting and staying connected–or not

There are moments in life and moments in careers that define who we are, who we become and who we once were.  This chapter about SQL Server connectivity actually brings to light two of those moments in my life. 

In no particular order, I will begin with career moment #1.  Meeting William Vaughn at DevConnections in Las Vegas and chatting with him for a while over a drink.  You know, there are some great folks with some great stories in this world… but when it comes to my career, listening to William Vaughn is akin to my three-year old daughter having cookies and hot chocolate with Santa Claus at the North Pole. 

Career moment #2:  I will never forget the conversation that I had with Microsoft around the proper and improper usage of the SA account in SQL Server.  For the record, I’m still right and William Vaughn agrees with me when he states:

WARNING: As a general rule of thumb, you should never expose the SA password nor create applications that use it. Do not permit developers to build applications using the SA account. Doing so masks any number of complex issues that will have to be addressed at some time in the future—hopefully before your data is compromised.

Microsoft still sells Great Plains (GP), aka, Dynamics and it STILL requires the SA password be known in order to accomplish many of the administrative functions within the application.  Appalling.  Version after version this has continued.  I do hope that they invest the time, money and resources into providing a secure financial package.

So back to getting and staying connected… This is a great chapter and one that I will be sure to share with developers.  There is a ton of good information in this chapter about the different ways to connect to SQL Server and options therein.  The one that stuck me the most was that in a connection pooling scenario, the connection remains dormant (server-side) for 4 to 8 minutes after the connection is “closed” via the Connection.Close method. 

In closing the author states that “developers want solutions, not options” and this chapter does indeed provide those solutions along with excellent rational for the solutions presented.


0 Responses to “Chapter 18 – Getting and staying connected–or not”

  1. Leave a Comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s


Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 11 other followers