Re: How to restrict access our DB on SQL server.
From: Angie (NoSpam_angie_kong_at_hotmail.NoSpam.com)
Date: 01/11/05
- Next message: Kam: "SQL Query Analyzer cannot bring up all the database in Object Brow"
- Previous message: Mary Chipman: "Re: Query Analyzer Adds Blank Line in Scripts of Objects"
- In reply to: paresh goyal via SQLMonster.com: "How to restrict access our DB on SQL server."
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 10 Jan 2005 17:39:48 -0800
Sounds like you're looking for a solution that might not exist. If your
users that currently use the applications login to SQL with their own
userids, they can use the same userids with any query tool and do whatever
they have permissions for. You could try to use different ports, server
aliases, etc.... to make it tougher for them to discover where the actual
sql db sits but it's just a speed bump, not a barrier.
aK.
"paresh goyal via SQLMonster.com" <forum@SQLMonster.com> wrote in message
news:d15479cc26b24cf0a782a131acead60a@SQLMonster.com...
> Hi,
> How can we restrict our DB if connecting thru other applications like SQL
query analyzer, Excel & even Enterprise manager?
> but this DB should be accessible by our application (from front end)
only...
> I learned about "Application Role" in SQL server 2000 but to apply this
> we will have to change our code thousand places.
>
> Have any idea...Pl. do suggest???
>
> Thanx in advance!!!!
>
> Regards,
> Paresh....
>
> --
> Message posted via http://www.sqlmonster.com
- Next message: Kam: "SQL Query Analyzer cannot bring up all the database in Object Brow"
- Previous message: Mary Chipman: "Re: Query Analyzer Adds Blank Line in Scripts of Objects"
- In reply to: paresh goyal via SQLMonster.com: "How to restrict access our DB on SQL server."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
