(function() { var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js'; (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(ga); })();
Home > SQL > CSS SQL Server Engineers : Did your backup program/utility leave your SQL Server running in an squirrely scenario?

CSS SQL Server Engineers : Did your backup program/utility leave your SQL Server running in an squirrely scenario?

October 7th, 2009 Kevin Leave a comment Go to comments

Did your backup program/utility leave your SQL Server running in an squirrely scenario?

My colleges asked me if ’squirrely’ is a technical term and for this post the answer is yes. CSS is not going to deny support to customers but SQL Server was not tested in this scenario so you may have chased yourself up a tree, hence I use the term squirrely.

SQL Server 2005 introduced snapshot databases and modified DBCC to create secondary snapshot streams for online DBCC operations. The online DBCC creates a secondary stream of the database files that is SPARSE. CSS has found that if a 3rd party backups and utilities or NT Backup is used against the database files the SPARSE setting may get incorrectly, propagated to the parent stream. In the case of DBCC this is the original database files(s).

Repro

via CSS SQL Server Engineers : Did your backup program/utility leave your SQL Server running in an squirrely scenario?.

Share and Enjoy:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • LinkedIn
  • Slashdot
Categories: SQL Tags: ,
  1. No comments yet.
  1. No trackbacks yet.

Powered by WP Hashcash