This is in continuation to the previous observation I had with backups in SQL Server 2014. Backups are such a mundane every task for a DBA that there hardly much to talk about. Infact in a lot of sessions I ask how many can take a backup in SQL Server, I get about all of them are so confident in using the same with few clicks via SSMS.
So with something as trivial as backup what can some of the message enhancement be? Interestingly, if you have ever taken a backup in the past you will see a number of informational messages. Some of these messages like the one below were always sent to the Errorlogs of SQL Server for records.
If you ever take a backup using T-SQL commands there is another interesting message that gets displayed which is lost after you close the results tab.
With SQL Server 2014, I found the above message being sent to the errorlogs and it is quite an handy information one can have. A typical message now sent would be:
BACKUP DATABASE successfully processed 298 pages in 0.026 seconds (89.261 MB/sec).
If that was not enough, I did a normal restore of the database and Woot !!! We get a similar message on the time it took to actually restore operation.
RESTORE DATABASE successfully processed 298 pages in 0.016 seconds (145.050 MB/sec).
I have personally felt the SQL Server Error Logs are a Pandora of information of your system health. It has amazing wealth of information that sometimes when you troubleshoot ticket for your SQL Server environments our support team generally also asks you to provide the Errorlogs as part of their dumps. With so much interesting information added, these enhancements are hardly noticed by DBA sometime.
PS: Click on the images to get a hi-res readable copy.
This entry was posted on Monday, March 17th, 2014 at 08:30 and is filed under Technology. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.