Re: SA Login
From: Boris Nikolaevich (boris@nikolaevich.mailshell.com)
Date: 08/15/02
- Next message: BP Margolin: "Re: Northwind and Pubs databases"
- Previous message: BP Margolin: "Re: SA Login"
- In reply to: Antony: "SA Login"
- Next in thread: BP Margolin: "Re: SA Login"
- Reply: BP Margolin: "Re: SA Login"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Boris Nikolaevich" <boris@nikolaevich.mailshell.com> Date: Wed, 14 Aug 2002 16:33:26 -0700
When you create a new instance of SQL Server 2000 on a given server, does
that create a different SA account for that instance?
If so, you could install a new instance of SQL Server, giving SA a custom
password for that new instance and load your proprietary DB in that new
instance.
That way, the client could go on his merry way administering the databases
in the default instance, and you would still have some additional
technological protection.
Of course, I haven't tried this, and I'm hoping someone can verify whether
this would work. Additionally, there's the SQL 2000 requirement--if you're
running an earlier version, this instancing idea won't work!
HTH,
Boris
"Antony" <mastersons@onetel.net.uk> wrote in message
news:27cd01c243c7$504fdfc0$39ef2ecf@TKMSFTNGXA08...
> We are using sql authentication, the client insists on
> having the SA login to maintain other dB's on the same
> server. Is there a way to deny the SA login access to a
> particular DB but maintain it's right for other DB's on
> the server.
> The built in NT login has been denied access.
>
>
>
- Next message: BP Margolin: "Re: Northwind and Pubs databases"
- Previous message: BP Margolin: "Re: SA Login"
- In reply to: Antony: "SA Login"
- Next in thread: BP Margolin: "Re: SA Login"
- Reply: BP Margolin: "Re: SA Login"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
