SEO

Are you seeing these errors frequently in the error log? Can you post an example? You might try disabling AUTOGROW for your database while your update job is running, since AUTOGROW can cause some concurrency issues that could manifest themselves as latch timeouts. Take a look at 310834 PRB: Common Causes of Error Message 844 or Error Message 845 (http://support.microsoft.com/?id=310834) for some more information.

Thanks
Ryan Stonecipher
Microsoft SQL Server Storage Engine.

"Daren Church" <d.church@marval.co.uk> wrote in message news:F2B0A1FB40ADD811A30B0050BA25A3E5D955@INETSRVR ...
We are experiencing a type 4 latch situation within our server
application under the situation where we are updating approx 90,000
records in one shot, with and without explicit transactions. Are there
any ways to program round this as this error has only recently appeared
after the efficiency of the server code has been made.

The MSDN tells us: As long as
<http://www.winnetmag.com/SQLServer/A...6/SQLServer_14
136.html#> SQL
<http://www.winnetmag.com/SQLServer/A...6/SQLServer_14
136.html#> Server carries on, and no other errors are being reported,
then there is usually nothing to worry about. They are merely showing
that the disk subsystem is unable to keep up with the level of i/o that
<http://www.winnetmag.com/SQLServer/A...6/SQLServer_14
136.html#> SQL Server is asking it to do. SQL just waits and retries
these requests. (The message *may* indicate that the disk subsystem is
experiencing problems - check the NT event log for scsi errors and any
hardware
<http://www.winnetmag.com/SQLServer/A...6/SQLServer_14
136.html#> monitoring tools you have)

We have also tried the service patch 3a, but this does not correct this
issue, does anyone have any ideas how to correct or program round.