Hello,
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.

Thanks

Hi

Can not be done. An Access DB password can be cracked in minutes.
Even if you could protect it, Profiler could trace what commands you send to
the DB.

Basic computer security principle: If someone has physical access to a
computer or a DB, they can get to the data on the PC or database.

Most good DBA's will come up with similar DB structures if they get asked to
create a DB to solve a problem. A DB structure can not be so "earth moving"
that it needs protection.

If a vendor supplies a product with a DB that is protected, for a good
laugh, I will want to look at it as they probably have bad design and worse
code to hide.

Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike@epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

"Parham" <parham.ghaffarian@gmail.com> wrote in message
news:1111934298.082322.13030@g14g2000cwa.googlegro ups.com...
> Hello,
> 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.
>
> Thanks
>

When you distribute your application, assume it will be an open book to
the end user. For both you and your users the best way to protect your
intelectual property is with a licence agreement, not with software
based security.

--
David Portas
SQL Server MVP
--

Parham (parham.ghaffarian@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, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp