choudhury.pradeep (12/22/2014)
The situation is not often on restart and occur rarely. Please clarify me, if the DB is in state of Restoring, can I recover the DB using command "restore database <Database name> with recovery"? As per my understanding the Slow recovery may be due to DB replication and related log files.
RECOVERING != RESTORING. That command works on a database that's in the RESTORING state. After restart a DB goes through RECOVERING, not RESTORING
Also Please suggest how it would be if the mirror/secondary DB set up in same server on a separate instance.
Um... You want a HA scenario to go down completely if a single component of a single server fails. Not very *high* availability is it?
Besides this if I set up mirroring / log shipping, in above scenario, i.e. if the DB gone for restoring state, what will happen to mirrored / secondary DB.
Depends on how you set the mirroring up, and it's not the RECOVERING state that's relevant, it's the restart. Log shipping, nothing happens.
Sorry for asking too many questions..
You need to do a *huge* amount of reading, you need to set these things up in lab environments and work with them until you're comfortable, before you even consider suggesting them for production. Otherwise you're setting yourself and your company up for failure.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability