SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


What if TDE was available in Standard Edition?


What if TDE was available in Standard Edition?

Author
Message
James Stover
James Stover
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1145 Visits: 862
I'm sure TDE will make it's way into lower versions - possibly even Express. Once Microsoft gets a whiff of 3rd parties (including their partners) muscling in on its turf they will cut them out faster than Steve Ballmer can say "Our stock price has dropped 10 cents". This has happened before, it will happen again. Just be patient.


James Stover, McDBA

Michael Valentine Jones
Michael Valentine Jones
One Orange Chip
One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)

Group: General Forum Members
Points: 26580 Visits: 11930
TravisDBA (7/6/2010)
I am talking about compressing the backup, not compressing the database then encrypting it,, But anyway, I don't remember seeing that anywhere in SQL 2008 BOL? That would be nice if that little important detail was in there, but what else is new. Smile


SQL Server 2008 Books Online does specifically mention that, but don't let that get in the way of a good gripe.


"SQL Server 2008 Books Online (August 2008)
Understanding Transparent Data Encryption (TDE)
...
Encrypted data compresses significantly less than equivalent unencrypted data. If TDE is used to encrypt a database, backup compression will not be able to significantly compress the backup storage. Therefore, using TDE and backup compression together is not recommended.
..."
TravisDBA
TravisDBA
SSCarpal Tunnel
SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)

Group: General Forum Members
Points: 4874 Visits: 3069
Thanks, but I already know about backing up a encrypted database with compression has no effect on the compression, and that is in BOL, hence my first post. However, it was pointed out in a previous post by Jay that compressing the database first then encrypting as an alternative. Where is that in BOL?, Anyway, I still don't like the idea of Mickeysoft giving us two new neat features we basically can't use together. Smile

"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ...:-D"
Ben Moorhouse
Ben Moorhouse
Right there with Babe
Right there with Babe (767 reputation)Right there with Babe (767 reputation)Right there with Babe (767 reputation)Right there with Babe (767 reputation)Right there with Babe (767 reputation)Right there with Babe (767 reputation)Right there with Babe (767 reputation)Right there with Babe (767 reputation)

Group: General Forum Members
Points: 767 Visits: 444
Michael Valentine Jones (7/6/2010)

SQL Server 2008 Books Online does specifically mention that, but don't let that get in the way of a good gripe.


Oh that made me chuckle! I love that kind of humour Smile
jay-h
jay-h
SSCertifiable
SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)

Group: General Forum Members
Points: 6009 Visits: 2441
TravisDBA (7/6/2010)
Thanks, but I already know about backing up a encrypted database with compression has no effect on the compression, and that is in BOL, hence my first post. However, it was pointed out in a previous post by Jay that compressing the database first then encrypting as an alternative. Where is that in BOL?, Anyway, I still don't like the idea of Mickeysoft giving us two new neat features we basically can't use together. Smile


My comment was not based on BOL, it was based the on the mathematics of compression and encryption. Compression works on mapping repetitive patterns in data, once encyrpted almost all such patterns are lost

...

-- FORTRAN manual for Xerox Computers --
Nadrek
Nadrek
SSCertifiable
SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)

Group: General Forum Members
Points: 7922 Visits: 2741
jay holovacs (7/7/2010)
TravisDBA (7/6/2010)
Thanks, but I already know about backing up a encrypted database with compression has no effect on the compression, and that is in BOL, hence my first post. However, it was pointed out in a previous post by Jay that compressing the database first then encrypting as an alternative. Where is that in BOL?, Anyway, I still don't like the idea of Mickeysoft giving us two new neat features we basically can't use together. Smile


My comment was not based on BOL, it was based the on the mathematics of compression and encryption. Compression works on mapping repetitive patterns in data, once encyrpted almost all such patterns are lost


Which is why all normal encryption software that's built for this first compresses (which, as a desirable side effect, reduces repetitive patterns in the data), and then encrypts! See PGP and GPG software, or any of the compression+encryption softare (7-Zip, PKWare Zip, WinZip, etc.) which use this ordering.

If your DB is encrypted but not compressed, then clearly one should have the option to spend the CPU time to decrypt, then compress, and then encrypt the compressed data, thus giving the effects of both. Since SQL Server compression doesn't take a whole lot of CPU anyway, this shouldn't be an unusual option to consider.
Michael Valentine Jones
Michael Valentine Jones
One Orange Chip
One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)

Group: General Forum Members
Points: 26580 Visits: 11930
Has anyone implemented table compression in conjunction with TDE?

What was the impact of compression and TDE on database size, compared to a database with just TDE or just table compression?


It would be nice if there was a separate option on the backup command to encrypt the backup file, with or without compression. That would be a more useful option for most customers than TDE.
TravisDBA
TravisDBA
SSCarpal Tunnel
SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)

Group: General Forum Members
Points: 4874 Visits: 3069
Nadrek (7/7/2010)
jay holovacs (7/7/2010)
TravisDBA (7/6/2010)
Thanks, but I already know about backing up a encrypted database with compression has no effect on the compression, and that is in BOL, hence my first post. However, it was pointed out in a previous post by Jay that compressing the database first then encrypting as an alternative. Where is that in BOL?, Anyway, I still don't like the idea of Mickeysoft giving us two new neat features we basically can't use together. Smile


My comment was not based on BOL, it was based the on the mathematics of compression and encryption. Compression works on mapping repetitive patterns in data, once encyrpted almost all such patterns are lost


Which is why all normal encryption software that's built for this first compresses (which, as a desirable side effect, reduces repetitive patterns in the data), and then encrypts! See PGP and GPG software, or any of the compression+encryption softare (7-Zip, PKWare Zip, WinZip, etc.) which use this ordering.

If your DB is encrypted but not compressed, then clearly one should have the option to spend the CPU time to decrypt, then compress, and then encrypt the compressed data, thus giving the effects of both. Since SQL Server compression doesn't take a whole lot of CPU anyway, this shouldn't be an unusual option to consider.



Exactly right Michael! My point is that Mickeysoft did not take time in the first place to consider this as others already do. If they had, then those two new features would have been able to be utilized together in the product, rather than separately. Smile

"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ...:-D"
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum







































































































































































SQLServerCentral


Search