naga.rohitkumar (11/21/2012)
awesome reply alivnfrom my point of view ithnk so if not please correct ----any one can suggest me------
coz inthis sort of scenarios only u will have two options
1. as mentioned by alivn
2. think for the solutions sort-out in parallel consult ur senior dba and windows team also
[1.check the error logs in sqlserver and event-viewer
2. check the disk-space issues
3.what ever the high availability it is running on first check ur sqlserver services running or not --- if not restart the services which takes min 15mins downtime.
2. restore the full backup or point in time restore (tlogbackup .trns )]
sorry if any wrong ideas shared am not highly experienced iam starter in this domain
I'm not sure who you are replying to and so I'm not sure which question you're trying to answer but bouncing the server should be an almost last resort and doing a restore is the absolute last resort. Whenever you do a restore, some data is lost and you might not be able to get it back especially if you don't have the room to keep the original and the restored database active at the same time.
--Jeff Moden
Change is inevitable... Change for the better is not.