Protecting/Encrypting DataBase Objects

My employer has asked me If I can encrypt the MS-SQL Views, Triggers and Stored Procedures in a clients database.  He mentioned that he has heard that MS-SQL can Encrypt database objects to stop other people coping them.  My Question is:   Is this possible?  if it is, how do I go about doing it? If it's not... how else can I secure a deployed DB?
KirkGrayAsked:
Who is Participating?
 
Victor SpiridonovConnect With a Mentor Commented:
You just need to add WITH ENCRYPTION statement to your create statements, here is an extract fro help.

CREATE TRIGGER [owner.]trigger_name
ON [owner.]table_name
FOR {INSERT, UPDATE, DELETE}
[WITH ENCRYPTION]
AS sql_statements

CREATE VIEW [owner.]view_name
[(column_name [, column_name]...)]
[WITH ENCRYPTION]
AS select_statement [WITH CHECK OPTION]

CREATE PROCedure [owner.]procedure_name[;number]
      [(parameter1 [, parameter2]...[parameter255])]
[{FOR REPLICATION} | {WITH RECOMPILE}
      [{[WITH] | [,]} ENCRYPTION]]
AS sql_statements


NOTE: You will not be able to edit objects, that you created  with this option, so you have to store the code somewhere else.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.