March 4, 2009 at 10:20 am
Hi
In my sql server 2000 i am having a db with 40 gb in simple recovery mode.since last one week i am facing a problem. after restarting the sql service the db is taking more time to become online .for a long time it is in recovery mode. Kindly help
March 4, 2009 at 10:25 am
What mode is it once the SQL service has been restarted?, is SQL service takes a long time to restart??
March 4, 2009 at 10:28 am
Hi
When we restarted the sql services other dbs came online fastly.Only one db taking more time to become online. it is in recovering state
March 4, 2009 at 10:44 am
hmm this is nothing to do with a recovery mode, if the database is on recovery mode then its trying to completed some uncompleted business before restart? is this a production database?? how often do you restart SQL services ??
March 4, 2009 at 10:57 am
HI
This is a production server. daily we are restarting the services.The problem start happening since last week
March 4, 2009 at 11:03 am
Out of curiosity, can i know the reason for restarting the service on a daily basics,
On the other hand, is there any code changes that have been made on application that access the database, check this, try to stop SQL server from configuration manager and then try to start it rather than restarting it.
Before restarting check how many threads were using that database. 🙂
March 4, 2009 at 11:33 am
HI
as per client request we are restarting the services.
March 4, 2009 at 3:01 pm
Do you ever run DBCC CheckDB against the production database causing issues for you? If not, it may be a good idea to check the overall health of the database from time to time but especially as soon as it's online, if possible. 40Gb is not a large database these days and you should be online withing a minute or two at most.
-- You can't be late until you show up.
March 4, 2009 at 3:05 pm
Hi
DBCC is running every sat
March 4, 2009 at 3:08 pm
And it always comes back without error I'm guessing?
-- You can't be late until you show up.
March 4, 2009 at 3:10 pm
Hi
Yes.The recovery issue is only for one db.all other are fine.
March 4, 2009 at 3:12 pm
binu.m a (3/4/2009)
HiYes.The recovery issue is only for one db.all other are fine.
Yeah, i understand that. CheckDB runs for one database (or potentially all, depending on your script). Anything in the SQL log, after it does come up? How about event logs on the server, anything odd there?
-- You can't be late until you show up.
March 4, 2009 at 3:16 pm
HI
Nothing on error log.
March 5, 2009 at 5:55 am
Please execute DBCC CHECKDB with ALL_ERRORMSGS,NO_INFOMSGS
MJ
March 5, 2009 at 6:10 am
Is the database in question on a separate physical disk(s) than the others? Have you checked event logs on the server to see if anything is going on hardware-wise?
-- You can't be late until you show up.
Viewing 15 posts - 1 through 15 (of 17 total)
You must be logged in to reply to this topic. Login to reply