Prev: database integrity checks failing
Next: Paging Size set up for sql 2005 best performance
From: Erland Sommarskog on 15 Jul 2010 17:30
RG (RG(a)discussions.microsoft.com) writes:
> It appears that as the server C problem is due to locking as the db in
> production and active transacitons are coming in. To test, I created the
> copy of prod db on the same server (C). This worked.

Interesting. One would think you would see blocking when working
against the production database. I do recognize the sympton: the
process from the linked server is there, but it gets nowhere. This
was more common some years back, when you had a mix of Win2000 and
Win2003.

--
Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

First  |  Prev  | 
Pages: 1 2
Prev: database integrity checks failing
Next: Paging Size set up for sql 2005 best performance