SqlServer Begin's

Past weekend I encountered a situation  where there was insufficient disk space due to logfull errors. As usual I identified the log file that needed to be shrunk and attempted to shrink the file. However, to my surprise it didn’t want to shrink and threw the following error. Msg 3023, Level 16, State 2, Line 1 Backup, 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. Following is the screenshot of the unused space of the database files For a moment I thought it was something wrong with the database. But later realised that there were conflict of interest to the logfile usage and whatever the operation that was using it. This could have been caused due to active transaction in the transaction log due to replication,mirroring , logshipping , some datamilipulation or a backup in progress. With...

I was recently attempting to re-establish mirroring for a client and realized the following waittype hanging on the database. I initially thought, the mirroring session was not removed correctly but after further verification it was soon obvious that the mirroring session had been discontinued and it was clean. When I attempt to kill the process PSID = 20 , I got the following message  Spid = 20 Msg 6107, Level 14, State 1, Line 1 Only user processes can be killed. At 2 am in the morning I was no mood for research , I was just interested in getting the mirroring session established and get to bed. I knew it was a matter of dropping the database and getting about with the normal business. Then I mistakenly executed the restore databases script !!!!. surprisingly the restore didn’t complain and progressed to complete without errors and I continued to setup the mirroring session, which completed successfully. Later during the day I discovered that...