Yes. You will want to check your database on a regular bases for integrity problems. You will want to catch problems when they first show up. If you don't you can end up loosing data when you repair the problem.
Denny
MCSA (2003) / MCDBA (SQL 2000)
--Anything is possible. All it takes is a little research. (Me)
The maintenance plan job for intergrity check has repair option, is this job used to detect integrity problem or fix intergrity problem? I don't understand how it works, if the database has no problem, this job will be successfule, if database does have problem, this job fail, Am I right?
The job will fail giving you details what caused it to fail. Like what page of database has the problem or sumthing like that. You could run the job manually first to check if you are getting any issues, and then you could schedule it.
I created a maintenence plan for a database and check every option in create maintenance plan wizard, then I looked the jobs directory in EM, I can't find any rebuild index maintenance job, how can I create this job?
I would not rebuild your indexes unless you really need to do so. Instead, about once a month, run DBCC INDEXDEFRAG.
What's the difference? Rebuilding the indexes is an 'offline' operation. The tables will be unavailable to your users. Defragging the indexes leaves the tables accessable.
Read the BOL for more information. You really should make the BOL your friend as it has lots of helpful information about SQL Server.
BOL=Books OnLine=Microsoft SQL Server's HELP
Installed as part of the Client Tools
Found at Start>Programs>Microsoft SQL Server>Books OnLine
or online at:
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.