experience Gerd Saurer on 14 Oct 2007 09:43 pm
Lock(MS SQL Server) - WSU
Our team is using the Microsoft SQL Server 2005 for nearly 2 Years now and I have to admit that its handling still surprises me sometimes. The application we are developing uses the database heavily for some scenarios and last week we had to recognize that some concurrent situations take the Server into an undefined state. At the moment we are developing on an Vista 64-Bit but we had tested it on Windows XP too. The interesting part was that some machines run into some kind of endless locking on the database and some didn’t. We invested hours analyzing the situation, when the locking issue occurred but we couldn’t find the problem. We tried lock hints, optimizing the SQL statements - all the stuff you can imagine but nothing worked out. In the end after several hours of searching through the web we found some Feedback in the MS Sql Server Connect site. I really like the term Feedback here - it does not speak about Bugs which most of them are. In the end it came out that the KB928365 Security Update for .NET Framework was the initiator of our problem. After de-installing it from the XP ad Windows 2003 Machines everything worked correct just on some Vista Machines we still have the same problems. The Security Update came out about 2 weeks ago so it was hard to find the problem - 2 weeks early everything worked correct.
Don’t get me wrong I like C# and the CLR and all the possibilities you have but in this situation you like self controlled environments where nobody other than you decide which version is used by you product.
