Re: Restrict access to SQL database through ODBC
From: kevin
Date: 06/27/02
- Next message: John Smith: "Configuration of Anti-Virus Software"
- Previous message: Chris Goddard: "Restrict access to SQL database through ODBC"
- In reply to: Chris Goddard: "Restrict access to SQL database through ODBC"
- Next in thread: Morris Lewis: "Re: Restrict access to SQL database through ODBC"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: <kevin> Date: Thu, 27 Jun 2002 07:55:43 -0700
Not very easily. If the application reports it's name to SQL (which they
don't all do), you could probably write a background job/service to kill
everything that connected to that database of a different application name
(sysprocesses..program_name)
"Chris Goddard" <cjg@exel.co.uk> wrote in message
news:12bfa01c21ddc$c06c7860$b1e62ecf@tkmsftngxa04...
> I have a third-party (client / server) application which
> requires access through an ODBC DSN to my SQL Server
> database. I would like the user's access to the database
> to be restricted to this application only. Since the app
> is a 3rd party app I cannot use application roles as I
> have no control over the connection and therefore cannot
> run sp_setapprole on that connection.
>
> Is there any way I can use the ODBC data source but hide
> it from other applications such as MSOFFICE which use
> ODBC. I would also like to prevent the user from setting
> up their own ODBC datasources which could point at the
> database server.
>
> Connection is using Integrated Security.
>
> Any advice welcome.
- Next message: John Smith: "Configuration of Anti-Virus Software"
- Previous message: Chris Goddard: "Restrict access to SQL database through ODBC"
- In reply to: Chris Goddard: "Restrict access to SQL database through ODBC"
- Next in thread: Morris Lewis: "Re: Restrict access to SQL database through ODBC"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
