October 31, 2002 at 11:38 am
I have a database called mesonet. I also have a maintenance plan. The recovery model is full. When the plan executes, check data & index linkages fails with error=7919 'database needs to be in single user mode'. also error=9002 for rebuilding indexes. Does anyone have a clue?
SQL2DAY
October 31, 2002 at 11:43 am
have you set it to "repair minor errors"?
Don't
Steve Jones
October 31, 2002 at 11:46 am
Read up on the Database Integrity Check. Attempts to repair any minor problems will puts the database in single user mode.
So I'm guessing your maintenance plan says to repair any minor problems, and someone is in the database when the maintenance plan is run.
Hope this helps.
Gregory Larsen, DBA
If you looking for SQL Server Examples check out my website at http://www.geocities.com/sqlserverexamples
Gregory A. Larsen, MVP
October 31, 2002 at 11:48 am
You have checked "attempt to repair minor problems" in the maintenance plan. The job putso put the database in single user mode, whether it needs to repair or not, and there is still a session open, so it cannot do that
Either you run the job at a time that there are no sessions open or you uncheck this option.
If the check does show problems , you can always run DBCC checkdb mesonet repair_fast by hand.
Joachim.
November 4, 2002 at 8:27 am
Thanks to all! That corrected the problem. The only thing now is I'm noticing the transaction log has doubled in size. My database size is 435 MB which encompasses one file titled mesonet_data=435MB. The transaction logs are as follows: mesonet_ log=201,
mesonet_1_log = 195mb, mesonet_2_log=24mb, mesonet_3_log=186mb, mesonet_4_log=195mb
My question is: How do I handle transaction file growth?? At what point can I delete them? What is the best course of action for backing up data?
Mitch
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply