August 3, 2011 at 12:07 am
Hello.
We have this connection string in one of our windows services and portal (C# .NET) develop by some other developer. I want to understand the connection string parameters, why we are using it, and what is the best solution in a clustered environment. Also, can we use any performance counters in case of debug situation to get better understanding of any failures?
data source=192.168.12.345;initial catalog=SAMPLE_DB;user id=SAMPLE_DB_USER;pwd=test;persist security info=False;workstation id=SAMPLE_MACHINE;packet size=4096;Connect Timeout=100;Min Pool Size = 0;Connection Lifetime=0” .
We are using .NET Framework 3.5 and Sql Server 2005 SE.
Any recommendations on the proper connection string is greatly appreciated. Thanks for the help!
August 3, 2011 at 9:09 am
This should help clear things up:
All SQL Server SqlConnection properties
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
August 3, 2011 at 10:00 am
opc.three (8/3/2011)
This should help clear things up:
Thanks for the response opc.three but I have read this similar article from here also:
However, if possible I would like some connection string values example that is suitable for clustered environment. Thanks!
August 3, 2011 at 10:26 am
Sorry, I guess I confused on your request. A connection string to a clustered instance will look very similar to one connecting to a stand-alone instance...that's the point of clustering, multiple instances are acting and are reachable as if they were only one instance. After having read what each connection string property means, including Connection Lifetime, what is your underlying concern?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
August 3, 2011 at 11:22 am
My concerns are:
1.) I want to know if each of the property specified in this connection string sample below is well suited for a clustered environment. e.g. The Connection Lifetime, why does it have to be zero(0)? The packet size, should it be set to some other number other than 4096 or this will do? The persist security info, should it be set to False and not true?
data source=192.168.12.345;initial catalog=SAMPLE_DB;user id=SAMPLE_DB_USER;pwd=test;persist security info=False;workstation id=SAMPLE_MACHINE;packet size=4096;Connect Timeout=100;Min Pool Size = 0;Connection Lifetime=0” .
2.) Can we use any performance counters in case of debug situation to get better understanding of any failures?
Thank you for your time and help opc.three.
August 3, 2011 at 11:32 am
James Tech (8/3/2011)
My concerns are:1.) I want to know if each of the property specified in this connection string sample below is well suited for a clustered environment. e.g. The Connection Lifetime, why does it have to be zero(0)? The packet size, should it be set to some other number other than 4096 or this will do? The persist security info, should it be set to False and not true?
data source=192.168.12.345;initial catalog=SAMPLE_DB;user id=SAMPLE_DB_USER;pwd=test;persist security info=False;workstation id=SAMPLE_MACHINE;packet size=4096;Connect Timeout=100;Min Pool Size = 0;Connection Lifetime=0” .
Is this you doing due diligence, or do you have a specific issue with the settings?
2.) Can we use any performance counters in case of debug situation to get better understanding of any failures?
Define "any failures". Are you seeing a specific error message in your SQL Server Error Log? Some unwanted behavior or message from your app?
Thank you for your time and help opc.three.
I am not sure I have helped much at all other thus far...other than to extend our dialogue in hopes of getting enough information out there so I or someone else can 🙂
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
August 4, 2011 at 10:05 pm
Thanks opc.three. Somehow I got some inputs from you. Again, thanks for helping.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply