Re: Encrypted database deployment
- From: petery@xxxxxxxxxxxxxxxxxxxx ("privatenews")
- Date: Wed, 23 Aug 2006 03:20:33 GMT
Hello Mike,
Agree with you that he shall be able to use ALTER SERVICE MASTER KEY
statment to change the master key of the server. However, changing SQL
server account might be more convenient to isolate the issue.
http://blogs.msdn.com/lcris/archive/2005/09/30/475822.aspx
BOL 2005 states:
?The service master key is automatically generated the first time it is
needed to encrypt a linked server password, credential, or database master
key. The service master key is encrypted using the local machine key or the
Windows Data Protection API. This API uses a key that is derived from the
Windows credentials of the SQL Server service account.
The service master key can only be decrypted by the service account under
which it was created or by a principal that has access to the Windows
credentials of that service account. Therefore, if you change the Windows
account under which the SQL Server service runs, you must also enable
decryption of the service master key by the new account.
Regenerating or restoring the Service Master Key involves decrypting and
re-encrypting the complete encryption hierarchy. Unless the key has been
compromised, this resource-intensive operation should be scheduled during a
period of low demand.
Changing the SQL Server Service Account To change the SQL Server service
account, we recommend that you use SQL Server Configuration Manager. This
tool performs the required decryptions and encryptions, and configures
other settings that SQL Server requires. In situations in which SQL Server
Configuration Manager cannot be used to change the service account, you can
use the ALTER SERVICE MASTER KEY statement to make the service master key
available to the new account
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
.
- References:
- Re: Encrypted database deployment
- From: Roger Wolter[MSFT]
- Re: Encrypted database deployment
- From: Roger Wolter[MSFT]
- Re: Encrypted database deployment
- From: Roger Wolter[MSFT]
- Re: Encrypted database deployment
- From: Gerhard
- Re: Encrypted database deployment
- From: Mike C#
- Re: Encrypted database deployment
- From: "privatenews"
- Re: Encrypted database deployment
- Prev by Date: Encrypted and Decrypted Conn Str....now what? beginner.
- Next by Date: Re: SQL Server 2005: Checking if Login is connected to any database
- Previous by thread: Re: Encrypted database deployment
- Next by thread: BOL ERROR: ALTER CERTIFICATE/ALTER ASYMMETRIC KEY
- Index(es):
Relevant Pages
|
|