http://www.sqlmag.com/authors/author/author/5777731/rsscomment/5777731en-USFri, 25 May 2012 09:08:24 GMTFri, 25 May 2012 09:08:24 GMThttp://www.sqlmag.com/article/log-files/after-the-crash#commentsAnchorTue, 09 Aug 2005 07:35:13 GMT
Excellent article]]>RANGATue, 09 Aug 2005 07:35:13 GMThttp://www.sqlmag.com/article/log-files/after-the-crash#commentsAnchorhttp://www.sqlmag.com/article/enterprise-manager/stay-in-control#commentsAnchorThu, 23 May 2002 00:55:19 GMT
Good article. I follow a similar paradigm and repeat on a fortnightly or monthly basis, depending on the rate of change. The key is to not forget logins and the CREATE DB statement etc. We also use the stored procedure versioning (e.g., CREATE PROCEDURE vyx;2). I tend to trust programmers with version management via standard headers and checking code into VSS as required (over and on top of standard full backups). Thanks, Ck]]>Chris Kempster Thu, 23 May 2002 00:55:19 GMThttp://www.sqlmag.com/article/enterprise-manager/stay-in-control#commentsAnchor