Can I prevent customers from viewing schema?

Hi all,
I'm struggling with the pros and cons of developing a new desktop app using
Jet or MSDE/SQL Server. If I use MSDE/SQL Server, my installer would need
to be able to either install MSDE (if it's not installed already) or locate
an existing SQL Server in which to create my database.
One thing that I would like to accomplish is a little protection of my
intellectual property. Specifically, I'd like to prevent customers from
looking at my database schema. Is this possible (or practical) in a
production SQL Server environment? If so, what is involved?
TIA!
- BobBob,
The schema definitions in a database are avialable to public, which means
that anyone can read them. Trying to subvert this would probably cause you
some real problems.
For the future: http://tinyurl.com/th9k "An Overview of SQL Server "Yukon"
for the Database Developer" makes the following interesting comment:
SQL Server "Yukon" ships with a new security model that separates users from
objects, provides fine-grain access and provides greater control of data
access. Additionally, all System tables are now implemented as Views,
providing greater control over database system objects.
Wait and see on that one, I guess.
Russell Fields
"Bob Altman" <rda@.nospam.com> wrote in message
news:ekz#SlWTEHA.384@.TK2MSFTNGP10.phx.gbl...
> Hi all,
> I'm struggling with the pros and cons of developing a new desktop app
using
> Jet or MSDE/SQL Server. If I use MSDE/SQL Server, my installer would need
> to be able to either install MSDE (if it's not installed already) or
locate
> an existing SQL Server in which to create my database.
> One thing that I would like to accomplish is a little protection of my
> intellectual property. Specifically, I'd like to prevent customers from
> looking at my database schema. Is this possible (or practical) in a
> production SQL Server environment? If so, what is involved?
> TIA!
> - Bob
>|||Thanks Russell.
"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message
news:e47QyGZTEHA.2128@.TK2MSFTNGP11.phx.gbl...
> Bob,
> The schema definitions in a database are avialable to public, which means
> that anyone can read them. Trying to subvert this would probably cause
you
> some real problems.
> For the future: http://tinyurl.com/th9k "An Overview of SQL Server "Yukon"
> for the Database Developer" makes the following interesting comment:
> SQL Server "Yukon" ships with a new security model that separates users
from
> objects, provides fine-grain access and provides greater control of data
> access. Additionally, all System tables are now implemented as Views,
> providing greater control over database system objects.
> Wait and see on that one, I guess.
> Russell Fields
> "Bob Altman" <rda@.nospam.com> wrote in message
> news:ekz#SlWTEHA.384@.TK2MSFTNGP10.phx.gbl...
> using
need[vbcol=seagreen]
> locate
>