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.
I’ve noticed that when viewing query results in a grid in SQL Server Management Studio, it often causes resource locking on the server, preventing other queries from running. Why does this happen, when I’m only opening the table for viewing and not for editing? Disconnecting the query window from the server releases the resources. I assume it doesn’t happen when I return the results as text, but I haven’t tested this yet.
What is the best practice for using query windows in SSMS?
What type of “resource locking on the server”? Running a
SELECTquery will hold read locks (that is normal behaviour).Read locks do not prevent other simple reads (SELECTs) from occurring.
Do you have other transactions occurring than have a
SERIALIZABLEisolation level?