Encrypt Stored Procs, Views, Etc. - hiding from other DBA

[TheBlueDog]

I have a database which I typically securely host on my own servers, but I am in the position of having to install it now on someone else's SQL Server. My preference is to completely hide the schema from prying eyes. I know in older versions of SQL at least you could encrypt all your procs, triggers, etc - is this possible in 2000? If so, how? Also, can I do anything to hide my table structure or views? Any suggestions on best way to hide this information on a server over which I have no administrative control would be appreciated.

 

[SonOfEmidec1100]

With sql 2000 its not possible to hide the schema from anyone with admin rights.

So called encrypted views/sp in any version of sql server (except maybe 2005 ?) can easily be decrypted.

 

[SQLSister]

This is one of the reasons why many COTS products don't use stored procedures even though they are more efficient. It will take less than five minutes to find out how to decrypt them with a google search.

The most effective way of keeping me from really understanding the schema of a COTS database I installed was the one developed in France with all the object names being in French. I could have figured out what mapped to what on the forms and the relationships if I had really tried but it wasn't worth the effort when all the field and table names were essentially meaningless to me.

Questions about posting. See faq183-874