Trying to open a SqlConnection in a try..catch block and capturing the SqlException if the login fails is a way to validate sql login. The problem with this method that we're running into is that the SqlConnection object is pooled. That is, if I change
password for a sql login then we've run into a scenario where the both the old and the new password allow us to connect to the database. This is bad.
Is there a more graceful method of validating login on both sql 2000/2005?
Thanks!
-
Follow
Oops, something didn't work.
Sign In to be begin to follow this thread
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.Getting "follow" information
Start following this thread
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.Removing your "follow"
Setting up your "follow"
Did you know you can
sign up for email notifications?
-
-
ADO.NET has pooling turned on by default... You have to disable this feature.
SO in essence you have your connection being pooled so your old login is still there in a sense.
Check on Connection Pooling on MSDN.
-
Yes, after I set the Pooling = false on the connection string, the problem was resolved. Thanks!
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.