Click here to Skip to main content
15,896,453 members

Comments by priy@ (Top 9 by date)

priy@ 1-Jun-11 8:49am View    
Thanks Dave...will look into it further
priy@ 1-Jun-11 6:03am View    
I am passing the same connection string i.e. "Integrated Security=SSPI;Initial Catalog=MYDatabase;Server=.\\SQLEXPRESS"
priy@ 1-Jun-11 6:02am View    
hOwever while simulating this problem i came across a strange behavior.
I have a small test application which opens SQL connection, waits for 8 ms and then closes that connection.
I am doing this in a while loop.
when thisi test app is running, I goto the task manager (under Processes tab) and kill sqlservr.exe.

I thought that now the test app should throw an exception, but it does not. it still opens and closes the sql connection.
How is that possible when the service itself is not running?
priy@ 1-Jun-11 6:01am View    
Deleted
hOwever while simulating this problem i came across a strange behavior.
I have a small test application which opens connection, waits for 8 ms and then closes connection.
I am doing this in a while loop.
when thisi test app is running, I goto the task manager (under Processes tab) and kill sqlservr.exe.

I thought that now the test app should throw an exception, but it does not. it still opens and closes the sql connection.
How is that possible when the service itself is not running?
priy@ 1-Jun-11 5:56am View    
No I do not have any named pipes enabled.
Thanks for the info...although it didnt help.