|
|
Posted by Erland Sommarskog on 10/01/01 11:38
kwdavids (kevin@davnet.org) writes:
> An argument against the memory corruption theory is that the problem
> straightens itself out after 30 seconds to a couple of minutes.
>
> This is really a very simple application (only 3 datasets total), and
> nothing else of any significance is running at the same time.
>
> It's as if SQL Server just stops responding from time to time (both to
> Enterprise Manager and my application). I can't find any locks, nor is
> the workstation using any CPU cycles.
Autogrow is a faint possibility, but an autogrow that takes that long
would extend the database with a couple of GB, and it does sound like
we are talking that size of the database.
One place to check is the SQL Server error log, to see if there are
any messages. Also look at the starting time of the log, so that it's
not the case that SQL Server stops and restarts.
Also check for things outside SQL Server. Do you run any disk defragmenter
or anti-virus?
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|