Database Maintenance

We are running SQL 2000 Enterprise Edition on Windows 2003 Standard Edition
Server. We setup a database maintenance (Database Integrity and Index,
Reorganize data and indexes, etc. ) to run every week. However, the report
shows that the maintenance job did not run because the database needs to be
in a single user mode. How do you setup a single user mode to run the
database maintenance? When the database maintenance is done, how do you
remove the single user mode? Thanks.Uncheck the "Attempt to repair minor problems" checkbox. All this does is
hide problems until they become unfixable.
Run DBCC CHECKDB manually. You will find you have a problem. Fix the
problem. You will likely have to take the system offline to fix it.
Database corruption issues are very often due to disk subsystem failures.
Check on that and repair if necessary.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:ubtudFMOGHA.2128@.TK2MSFTNGP10.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Edition Server. We setup a database maintenance (Database Integrity and
> Index, Reorganize data and indexes, etc. ) to run every week. However,
> the report shows that the maintenance job did not run because the database
> needs to be in a single user mode. How do you setup a single user mode to
> run the database maintenance? When the database maintenance is done, how
> do you remove the single user mode? Thanks.
>|||Thanks very much for your prompt response, Geoff.
If I run DBCC CHECKDB manually, what kind of problems do you expect that I
will encounter? Normally, are these problems easy to fix? Thanks.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23h63CRMOGHA.2268@.TK2MSFTNGP09.phx.gbl...
> Uncheck the "Attempt to repair minor problems" checkbox. All this does is
> hide problems until they become unfixable.
> Run DBCC CHECKDB manually. You will find you have a problem. Fix the
> problem. You will likely have to take the system offline to fix it.
> Database corruption issues are very often due to disk subsystem failures.
> Check on that and repair if necessary.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:ubtudFMOGHA.2128@.TK2MSFTNGP10.phx.gbl...
>|||How do you take the system offline to fix a problem?
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23h63CRMOGHA.2268@.TK2MSFTNGP09.phx.gbl...
> Uncheck the "Attempt to repair minor problems" checkbox. All this does is
> hide problems until they become unfixable.
> Run DBCC CHECKDB manually. You will find you have a problem. Fix the
> problem. You will likely have to take the system offline to fix it.
> Database corruption issues are very often due to disk subsystem failures.
> Check on that and repair if necessary.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:ubtudFMOGHA.2128@.TK2MSFTNGP10.phx.gbl...
>|||Answering both responses.
I don't know what kinds of problems you will find. You can run DBCC CHECKDB
anytime, but it does create a significant load on the system. I would do it
at a low activity time. To do a repair, you first have to take the database
into single-user mode. Both topics are covered in BOL under DBCC CHECKDB
and DBCC DBREPAIR. I suggest you do a LOT of reading before trying
anything.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:OLSGtcMOGHA.3924@.TK2MSFTNGP14.phx.gbl...
> How do you take the system offline to fix a problem?
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:%23h63CRMOGHA.2268@.TK2MSFTNGP09.phx.gbl...
>|||Thanks very much for your prompt response, Geoff.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OKBZgjMOGHA.3576@.TK2MSFTNGP15.phx.gbl...
> Answering both responses.
> I don't know what kinds of problems you will find. You can run DBCC
> CHECKDB anytime, but it does create a significant load on the system. I
> would do it at a low activity time. To do a repair, you first have to
> take the database into single-user mode. Both topics are covered in BOL
> under DBCC CHECKDB and DBCC DBREPAIR. I suggest you do a LOT of reading
> before trying anything.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:OLSGtcMOGHA.3924@.TK2MSFTNGP14.phx.gbl...
>