Protect DataBAse which is distributed on many SQL Servers

Hi,
I need to protect SQL Server 2000 database which I will distrubute to many
of my customers on their own SQL Servers. Unfortunately I still can't find a
way to solve this issue. Would you please help me with this?
Many thanks in advance!
Best regards,
Mariyan GotsevProtect in what way? What is it exactly you wish to prevent?
Andrew J. Kelly SQL MVP
"Mariyan" <mgms@.dir.bg> wrote in message
news:OblbpQPxDHA.2340@.TK2MSFTNGP12.phx.gbl...

quote:

---

>
> --
> Hi,
> I need to protect SQL Server 2000 database which I will distrubute to many
> of my customers on their own SQL Servers. Unfortunately I still can't find

---

a

quote:

---

> way to solve this issue. Would you please help me with this?
> Many thanks in advance!
> Best regards,
> Mariyan Gotsev
>
>

---

|||If you want to protect sql code of your procedures, triggers and views you
can use SQL Shield. http://www.activecrypt.com/sqlshield_howto.html|||Hi,
I have an application true which I want database to be available only. I
need to prevent every one of my customers from any access to the data in
the database, as there I put important customer information and customer
related restrictions - do the customer have rights to use some application
modules or not like example. What I need is very similar to MS Access
database password. You just can't open the database on every one machine if
you have not the database password. But for SQL Server this simple
protection seems to be much more difficult to implement. Please help me.
Many thanks!
Best regards,
Mariyan Gotsev
"Andrew J. Kelly" <sqlmvpnoooospam@.shadhawk.com> wrote in message
news:%2344QlrRxDHA.4060@.TK2MSFTNGP11.phx.gbl...

quote:

---

> Protect in what way? What is it exactly you wish to prevent?
> --
> Andrew J. Kelly SQL MVP
>
> "Mariyan" <mgms@.dir.bg> wrote in message
> news:OblbpQPxDHA.2340@.TK2MSFTNGP12.phx.gbl...
many[QUOTE]
find[QUOTE]
> a
>

---

|||Hi,
I have an application true which I want database to be available only. I
need to prevent every one of my customers from any access to the data in
the database, as there I put important customer information and customer
related restrictions - do the customer have rights to use some application
modules or not like example. What I need is very similar to MS Access
database password. You just can't open the database on every one machine if
you have not the database password. But for SQL Server this simple
protection seems to be much more difficult to implement. Please help me.
Many thanks!
Best regards,
Mariyan Gotsev
"Andrey Kubyshev" <email.ANTISPAM@.vtc.ru> wrote in message
news:brrq4s$ep3$02$1@.news.t-online.com...

quote:

---

> If you want to protect sql code of your procedures, triggers and views you
> can use SQL Shield. http://www.activecrypt.com/sqlshield_howto.html
>

---

|||To gain access to the database, you need a login defined with access
granted to a particular database. This is similar to Accessing
a secured Access database. Local machine admins by default have sysadmin
permission. You can change this:
http://www.microsoft.com/sql/techin...ration/May3.asp
If you're distributing your application with MSDE, you can disable all
network protocols during the install.
This means that only a locally logged on user can access the database.
See: DISABLENETWORKPROTOCOLS
810826 INF: New Switches in MSDE Service Pack 3 Setup
http://support.microsoft.com/?id=810826
You may want to consider using Application Roles to control security to the
database.
See: Establishing Application Security and Application Roles in SQL Books
Online.
In addition you should read this technet article before deploying your
application.
http://www.microsoft.com/technet/tr...chnet/prodtechn
ol/sql/maintain/security/sp3sec/SP3SEC03.ASP
Some addtional checklists :
http://msdn.microsoft.com/library/d...-us/dnnetsec/ht
ml/CL_SecDBSe.asp
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.