January 9, 2007 at 7:05 am
If SQL Server must be re-installed, and databases are reloaded from backup, what is the effect on the Service Master Key, in particular, and on individual Database Master Keys as well? If the SMK is created at installation, isn't it unique? Or does this scenario imply that a restore to a new instance must decrypt the backup and re-encrypt with the new SMK on INSERT or bulk copy? (Also, I understand that both SMK and DMKs can be 'backed-up', but I have not seen an example of their 'restore'.)
January 9, 2007 at 9:50 am
Found an earlier reference for SQL 7/2000:
Question posted by Ken Powers 8/19/2005 in forum Sql Server 7,2000 General; answered by 'Veteran' (Michelle) 8/22/2005 (followed by Ken's reply 'that's works!'):
Microsoft's knowledgebase(support.microsoft.com) shows this behavior is what they intend:
http://support.microsoft.com/default.aspx?scid=kb;en-us;814574
Take a look in Books Online at "Shrinking the Transaction Log".
What I have done in the past is use
backup log databasename with truncate_only
then use the DBCC SHRINKDATABASE command. It will only work if all the transactions are at the beginning of the log file. http://www.mssqlserver.com/faq/logs-shrinklog.asp
January 9, 2007 at 9:53 am
An even better thread in SQL Sever 7,200 Administration -- begun by Alphabet on 10/8/2004 !
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply