June 28, 2005 at 1:53 pm
June 28, 2005 at 2:06 pm
SQL Server is very picky whenit comes to timings and sometimes on High-End systems it can trigger that error during AUTOGROW (which you should avoid at all costs) and File Locking functions.
There is a solution HotFix which was included in SP4:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;815056
If you feel confortable with SP4 then go ahead and apply it other wise contact MS to obtain the HotFix only
hth
* Noel
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply