How i can Secure my database file from to be attached to
any other SERVER (sql server ) and view database design
Thanks"Said Fadel" <saidfadel@.hotmail.com> wrote in message
news:265001c4c104$ad703b20$a401280a@.phx.gbl...
> How i can Secure my database file from to be attached to
> any other SERVER (sql server ) and view database design
Are you asking, can your SQL Server 2000 database (and log) files be moved
to another remote server, keeping SQL Server on the original server? If so,
the database data and log files need to be keep on drives that appear to be
local to SQL Server, however these drives could be SAN attached.
Steve|||Typically this is done by securing access to the server itself - who
can access the directories where the data and log files are, who can
stop and start services, etc.
If you are referring to having a database that you give to a customer
and you don't want that customer to be able to view your design.
Likely the best was to manage this is through legal agreements.
Outside of that, you can look at some encryption mechanisms. You can
find links for these products in the encryption section of this FAQ:
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=22
-Sue
On Tue, 2 Nov 2004 09:52:10 -0800, "Said Fadel"
<saidfadel@.hotmail.com> wrote:
>How i can Secure my database file from to be attached to
>any other SERVER (sql server ) and view database design
>Thanks|||I want to deploy a SQL server database on my client windows 2003 server
; I
will have admin access on the server through Terminal services
The client server will have SQL server 2000 installed ; and I will use a
backup copy of my db and install it using Restor Database command in the
Enterprise manager
How can prevent my client from viewing/modifing my Database while he
has
admin access to the server ?
The database will host information relative to an ASP.net website that
is
hosted on IIS on the same server ; a username/password for this DB
should be
available also on the web.config file of the ASP.net website .. what is
the
minimum security setting that should be given to this username/password
to
allow the website manipulate the database ?
Please advice about that ; the reason I want to do this is to prevent my
client from reverse engineering my system analysis and databse design;
but
at the same time being able to use my ASP.net web application .
.
How can prevent my client from viewing/modifing my Database while he has
admin access to the server ?
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment