Parham (pa***************@gmail.com) writes:
How to protect structures(Tables,SP,Views and Functions) of a SQL
Server Database?(Password protect a database file)
I have a SQL database that will distribute with my application, I want
to protects it's structure from my appliction users. Only my
application can access the database.
You can use WITH ENCRYPTION on stored procedures, views and functions
when you create your objects. However, decryption methods can easily
be found on the web, so it gives no real protection. The main point
with encrypting objects is to inform people that they are supposed
to keep their nose out, so they don't wander just by chance into
your code. Someone who is dead set to find out what your code is like,
will be able to crack it.
And note that there might be one more reason to break into the code, not
only to steal intellectual property. The users might experience severe
performance problems, and need to tune your code, and you might have
gone for a two-month roundtrip in Argentina. In this case, the users
may be less happy with you if you have encrypted the procedures.
Anyway, as other have pointed out, encryption or not, a real license
agreement is a must.
And, oh, table definitions you cannot encrypt.
--
Erland Sommarskog, SQL Server MVP,
es****@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp