Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
// MS SQL Server 2008.
My application has several different connections to sql server database (C#, ADO .NET). Each connection uses the same user name and password. Some connections may execute simultaneously.
Is there any problem with that ? Should I add some settings to support that functionality ?
Is there any settings in connection string that allow/restrict simultaneous connections ? Is there any settings in SQL Server that allow/restrict that functionality ?
No this is normal. Using the exact same connection string also helps with pooling the connections (In the background your connections to the DB are kept open and reused rather than completely closing and opening them).