Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
irwan
Starting Member
3 Posts |
 Posted - 2008-01-22 : 23:49:22
|
| Dear all,I have some few questions regarding the encryption in SQL 2005. Does anyone know why it's not allowed to encrypt the entire data in the database? What is the impact if I insist on encrypting the entire data? Why the asymmetric method is more secure than the symmetric method? Does that mean symmetric method is more vulnerable?Thanks,Irwan |
|
|
alakiran
Starting Member
14 Posts |
Posted - 2008-01-23 : 02:40:03
|
| If you are creating a stored procedure and you want to make sure that the procedure definition cannot be viewed by other users, you can use the WITH ENCRYPTION clause. The procedure definition is then stored in an unreadable formAfter a stored procedure is encrypted, its definition cannot be decrypted and cannot be viewed by anyone, including the owner of the stored procedure or the system administrator. |
 |
|
|
irwan
Starting Member
3 Posts |
Posted - 2008-01-23 : 04:48:25
|
| Thanks Alakiran,what I ment was the data inside the table. If all the data in all of the existing table in the database are encrypted, will there be any negative impact?Regards,irwan |
|
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2008-01-23 : 06:10:40
|
| yes you'll have to decrypt it when searching it. indexes will be useless._______________________________________________Causing trouble since 1980blog: http://weblogs.sqlteam.com/mladenpSSMS Add-in that does a few things: www.ssmstoolspack.com <- new version out |
|
|
|
|
|
|
Encrypting The Entire Data