SQL Server SP4 Woes
One of our clients upgraded their SQL Server to SP4 and a procedure that was running fine till SQL Server SP3a suddenly gave an “access violation” error. On searching the internet, it looks like this was a problem earlier in SP3a (under some conditions) that was fixed in SP4! The interesting thing was that the code ran fine when you set the “Max Degree of Parallelism” to 1 (from its default value of 0). Not sure if anyone has ever faced this problem, but we are anxiously waiting for the SQL dumpe from the client, since as the saying always goes: We were not able to replicate it here, in our office on multi-processor machines with the “Max Degree of Parallelism” set to both 1 and 0. The code runs just fine!