DB Maintenance & Single-User Mode

SQL Server 2000 SP3 running on Windows Server 2003. The machine is a
quad-Xeon 2.2 GHz with 4 GB of RAM.
The SQL Server instance has 4 non-system databases, including the SharePoint
Services content database. We've been running, at 2:00 AM, weekly complete
backups and nightly transaction log backups--with integrity checks and
optimizations.
Every morning, we find that only the SharePoint database has been set to
"Single User" restricted access. Every time, the log shows:
"DBCC CHECKDB (STS_1182080930, repair_fast) executed by NT AUTHORITY\SYSTEM
found 0 errors and repaired 0 errors."
The links below point to related information. This appears to have been a
bug in SQL Server 7. Is it still a bug in SQL Server 2000 SP3?
Thanks,
Jim
"FIX: SQLMaint.exe Sets Database Status Incorrectly"
http://support.microsoft.com/defaul...kb;EN-US;276234
"a problem about repair damaged database and single user mode"
de&hl=en&l
r=&ie=UTF-8&selm=etEeJupv%24GA.176%40cppssbbsa01.microsoft.com&rnum=5" target="_blank">http://groups.google.com/groups? q=...soft.com&rnum=5Yes but it's not necessarily a good idea to use that option
and you'd probably want to clear the Attempt to repair any
minor problems check box in the maintenance plan.
If you get DBCC errors, you'd want to manually intervene and
do some type of root cause analysis. Then proceed with
whatever action from there.
-Sue
On Mon, 30 Aug 2004 16:29:38 -0500, "Jim Moon"
<jmoon()at()uab.edu> wrote:

>SQL Server 2000 SP3 running on Windows Server 2003. The machine is a
>quad-Xeon 2.2 GHz with 4 GB of RAM.
>The SQL Server instance has 4 non-system databases, including the SharePoin
t
>Services content database. We've been running, at 2:00 AM, weekly complet
e
>backups and nightly transaction log backups--with integrity checks and
>optimizations.
>Every morning, we find that only the SharePoint database has been set to
>"Single User" restricted access. Every time, the log shows:
>"DBCC CHECKDB (STS_1182080930, repair_fast) executed by NT AUTHORITY\SYSTEM
>found 0 errors and repaired 0 errors."
>The links below point to related information. This appears to have been a
>bug in SQL Server 7. Is it still a bug in SQL Server 2000 SP3?
>Thanks,
>Jim
>"FIX: SQLMaint.exe Sets Database Status Incorrectly"
>http://support.microsoft.com/defaul...kb;EN-US;276234
>
>"a problem about repair damaged database and single user mode"
>de&hl=en&
lr=&ie=UTF-8&selm=etEeJupv%24GA.176%40cppssbbsa01.microsoft.com&rnum=5" target="_blank">http://groups.google.com/groups? q=...soft.com&rnum=5
>|||Thank you, Sue.
Jim
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:8gq7j0pemr387cd2csrsainr9v11a0npf6@.
4ax.com...
> Yes but it's not necessarily a good idea to use that option
> and you'd probably want to clear the Attempt to repair any
> minor problems check box in the maintenance plan.
> If you get DBCC errors, you'd want to manually intervene and
> do some type of root cause analysis. Then proceed with
> whatever action from there.
> -Sue
> On Mon, 30 Aug 2004 16:29:38 -0500, "Jim Moon"
> <jmoon()at()uab.edu> wrote:
>
>