![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
from application owner point of view, there is an issue to protect database logic and structure from stealing. I'm pretty sure that was impossible to do (at least not easy to do) on MSSQL2000 and MSSQL2005, but what about MSSQL2008? MSSQL2008 has possibilty of transparent encryption backup so backup could be protected very efficiently, what about database structure and logic, is it possible to hide it from sql system admin? |
#3
| |||
| |||
|
|
m (web12master (AT) gmail (DOT) com) writes: from application owner point of view, there is an issue to protect database logic and structure from stealing. I'm pretty sure that was impossible to do (at least not easy to do) on MSSQL2000 and MSSQL2005, but what about MSSQL2008? MSSQL2008 has possibilty of transparent encryption backup so backup could be protected very efficiently, what about database structure and logic, is it possible to hide it from sql system admin? You can never hide anything from a system admin. The point with TDE is to protect data at rest. If someone manages to get hold of the database files or database backup without having the encryption key, he is not able to access the data. But if the user is able to connect to the server and has permissions enough, he can also see tables and procedures. And someone on the server needs to have that protection. It also worth pointing out that TDE is only available in Enterprise Edition. The proper way to protect intellectual property is through license agreements. The only possible solution from a technical point of view is to host the application yourself - which of course is an immense investment. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/pro...ads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinf...ons/books.mspx |
![]() |
| Thread Tools | |
| Display Modes | |
| |