Yes, it is the "transparent" encryption, which to me is "automatic" since when you tell it to encrypt, it automatically happens without any need for app changes or other changes. You say it is scheduled for a future CTP. That is what I needed to know.
Do you know any more about this feature, or where I can find information about it. For instance, is the encryption based somehow on the service or machine, where if the database is moved to another machine it could not be successfully re-attached unless it was unencrypted by someone knowing the password on the original machine first, or by the SQL Server Manager.
Thanks!
Hi, thank you for your interest. This is indeed slated for a later CTP. Regarding the re-attach, the detached database is still encrypted. To use this on a new server, you would need to migrate (backup and restore) the certificate protecting the data to your new server as well. Otherwise, the reattach will fail. This is not handled by SQL Server Manager; this is a user controlled process.
Please let me know if you would like further info or have any more questions.
Thanks,
Sung
Will the Express version have the same encryption features? If not, what will be missing? We would like to choose SQL 2008 Express to be part of a mobile solution, and having encryption features would make it a slam dunk. Thanks
Hi Rodney,
Thanks for your interest. We are only considering the transparent encryption feature for Enterprise Edition at this time and no plans have been announced to support any other SKU.
The encryption features introduced in SQL Server 2005 will continue to be availble on all SKU's.
Thanks,
Sung
Hi Sung,
I am interested in how SQL Server is handling the Key Management part(Encryption/Decryption/Signing). I appreciate if you provide some document or link to document which explains theoritical/functionality part of SQL Server 2008 key management.
Looking for some response.
Regards
Umesh Bansal
Hi Umesh,
SQL Server 2008 will be introducing a new feature called "Extensible Key Management" (EKM) which allows for third party cryptographic providers and key stores to be used alongside the encryption and key management shipped as part of the server. Does your question relate to the EKM feature or general SQL Server key management?
For general SQL Server key management documentation, please refer to (NOTE: this is unchanged from SQL Server 2005):
http://msdn2.microsoft.com/en-us/library/ms189586.aspx
There is a also a TechNet presentation available:
Hope this helps,
Sung