Monday, June 3, 2013

[MS SQL Server] Production Database in Suspect Mode...

[MS SQL Server] Production Database in Suspect Mode...


Production Database in Suspect Mode...

Posted: 03 Jun 2013 05:26 AM PDT

Production Database in Suspect Mode...Luckily we switched the nodes and working on other but trying to find the root cause of it.Here are the logs Can any one help me with it.05/30/2013 04:03:48,spid251,Unknown,The log for database 'XXXXXXX' is not available. Check the event log for related error messages. Resolve any errors and restart the database.05/30/2013 04:03:48,spid251,Unknown,Error: 9001<c/> Severity: 21<c/> State: 1.05/30/2013 04:03:48,spid254,Unknown,The log for database 'XXXXXX' is not available. Check the event log for related error messages. Resolve any errors and restart the database.05/30/2013 04:03:48,spid254,Unknown,Error: 9001<c/> Severity: 21<c/> State: 1.05/30/2013 04:03:48,spid244,Unknown,The log for database 'XXXXXXX' This not available. Check the event log for related error messages. Resolve any errors and restart the database.05/30/2013 04:03:48,spid244,Unknown,Error: 9001<c/> Severity: 21<c/> State: 4.05/30/2013 04:03:48,spid5s,Unknown,LogWriter: Operating system error 170(The requested resource is in use.) encountered.05/30/2013 04:03:48,spid5s,Unknown,Error: 17053<c/> Severity: 16<c/> State: 1.05/30/2013 04:03:48,spid5s,Unknown,Write error during log flush.05/30/2013 04:03:48,spid5s,Unknown,LogWriter: Operating system error 170(The requested resource is in use.) encountered.05/30/2013 04:03:48,spid5s,Unknown,Error: 17053<c/> Severity: 16<c/> State: 1.05/30/2013 00:00:11,spid22s,Unknown,This instance of SQL Server has been using a process ID of 2508 since 5/29/2013 3:56:31 PM (local) 5/29/2013 7:56:31 PM (UTC). This is an informational message only; no user action is required.

How to Restore a DB from one instace to Another

Posted: 03 Jun 2013 05:05 AM PDT

hello every one I need help...I have two Instance. Instace A and Instance B. I need to restore a backup that are store in instace Ato instance B. how can use the command restore database.thank you.

Backups failing after full transaction log

Posted: 02 Jun 2013 04:12 PM PDT

The sequence of events went like this.Transaction log disk ran out of space. I was able to add space to the drive. I then manually increased the space of the database log file that ran out of space through SSMS. That was successful. The file increased on the previously full disk.I tried to run my transaction backup jobs but backup files were never written. I canceled this job.I had previously canceled a scheduled transaction log backup job that was running since the disk filled up.I tried to run a manual backup on a small database bit am getting the below error. Msg 3023, Level 16, State 2, Line 11Backup, file manipulation operations (such as ALTER DATABASE ADD FILE) and encryption changes on a database must be serialized. Reissue the statement after the current backup or file manipulation operation is completed.My server log file was huge, crashing SSMS or any text editor. I ran sp_cycle_errorlog and created a new log.All I see now is: BACKUP failed to complete the command BACKUP DATABASE dba. Check the backup application log for detailed messages. Any suggestions?

Questions on Index Rebuilding (not reorganize)

Posted: 02 Jun 2013 11:07 PM PDT

Hi Guys,Need some information on Index Rebuilding. (sort_in_tempdb = off)When performing index rebulding (for indexes > 30% fragmented), will we expect to see an increase in the user transaction log size (LDF)? Or we will expect to see an increase in the database size instead (MDF)?Anyway to calculate how much size needed for rebuilding indexes?Let's say if i need to rebuild 3 indexes, each about 5 GB.After rebuilding the first index, will the temporary space used for rebuilding the first index be reuse for the 2nd index? Or we first need to perform a transaction log backup before the space can be reused?thanks!

shrinking tempdb log file

Posted: 03 Jun 2013 12:12 AM PDT

Last week our tempdb log file grew in size and alerts started pouring in as we have just few space left on the drive. Now we have free space in the log file. Can I release the space to the OS ? If the file is used and if we issue a truncate command we will have consistency issues ........can we do it if free space is available?

No comments:

Post a Comment

Search This Blog