Re: Secure a SQL-Server 2000 database.
From: Peter A. Schott (pschott@drivefinancial.com)
Date: 01/20/03
- Next message: Rita Nikas [MSFT]: "Re: IIS & SQL, NT authentication for Web"
- Previous message: Cory: "DTS and Job Security"
- In reply to: Ingar Eide: "Re: Secure a SQL-Server 2000 database."
- Next in thread: Ingar Eide: "Re: Secure a SQL-Server 2000 database."
- Reply: Ingar Eide: "Re: Secure a SQL-Server 2000 database."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: Peter A. Schott <pschott@drivefinancial.com> Date: Mon, 20 Jan 2003 16:33:23 -0600
Well, if you have initial rights to the server and can control which account
SQL Server runs under, you could always log in as that user, encrypt the
files, and set SQL Server to run under that account.
It works, but it may not be the best way to handle it. Besides, if the user
can change that password, they can still mess with the database.
Just some thoughts.
-Pete
ingar@eide.gs (Ingar Eide) wrote:
> Mary Chipman <mchip@nomail.please> wrote in message news:<l2eg2vcjb8bsorb4fllug7jthqlktja64b@4ax.com>...
> > You can't secure a database from a sysadmin on an instance of SQL
> > Server. If you have the ability to install your own named instance on
> > a client site, you could do it that way by not allowing the client to
> > have sysadmin access to that instance.
>
> Yes, I do that.
> But if the client stops the server, and copy the files to another
> SQL-Server-instance where he has an sysadmin, he can just use
> sp_attach_db, and then he has full access to my db.
>
> Ingar.
- Next message: Rita Nikas [MSFT]: "Re: IIS & SQL, NT authentication for Web"
- Previous message: Cory: "DTS and Job Security"
- In reply to: Ingar Eide: "Re: Secure a SQL-Server 2000 database."
- Next in thread: Ingar Eide: "Re: Secure a SQL-Server 2000 database."
- Reply: Ingar Eide: "Re: Secure a SQL-Server 2000 database."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|