Failed integrity check

The accounting system we support runs on SQL 2000. We have setup a SQL Job that checks the integrity of a each accounting database each evening. After running successufully for a few weeks the job started retuning a failed message. I checked the job log and the reason for the failure was because one of the databases couldn't be set to single user mode. When I first saw this I figured OK someone forgot to logout before leaving for the night. When discussing this with the accounting staff, they swear this couldn't be the case with this particular database since only 1 person accesses it and then only rarley, and he says he hasn't been in for days. The amount of activity in this database is minimal
The server was cycled and eveything ran fine for about 3 weeks. Then the same thing happned again over a span of a few nights consecutive. The are no overnight business processes. There are database backups that are scheduled in the evening, including one for this particualr database. Nothing is showing in the active processes during the day to this database, i.e. no run away processes. Any ideas on what is causing the SQL Server to think there is a open connection to this database?
Thanks much for any ideas!If these jobs are set up through maintenance plans, remove
the option for Attempt to repair any minor problems.
You really don't want this to run automatically anyway. If
you have problems with DBCCs, you should be investigating
the cause first before taking any action.
-Sue
On Sat, 18 Oct 2003 12:41:04 -0700, "DL"
<anonymous@.discussions.microsoft.com> wrote:
>The accounting system we support runs on SQL 2000. We have setup a SQL Job that checks the integrity of a each accounting database each evening. After running successufully for a few weeks the job started retuning a failed message. I checked the job log and the reason for the failure was because one of the databases couldn't be set to single user mode. When I first saw this I figured OK someone forgot to logout before leaving for the night. When discussing this with the accounting staff, they swear this couldn't be the case with this particular database since only 1 person accesses it and then only rarley, and he says he hasn't been in for days. The amount of activity in this database is minimal
>The server was cycled and eveything ran fine for about 3 weeks. Then the same thing happned again over a span of a few nights consecutive. The are no overnight business processes. There are database backups that are scheduled in the evening, including one for this particualr database. Nothing is showing in the active processes during the day to this database, i.e. no run away processes. Any ideas on what is causing the SQL Server to think there is a open connection to this database?
>Thanks much for any ideas!