Re: SQL Security

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Keith Kratochvil (sqlguy.back2u_at_comcast.net)
Date: 03/30/04 

Date: Tue, 30 Mar 2004 14:35:20 -0600

Perhaps you could look into using application roles. Here is a snippet from Books Online (within the SQL Server program group):

Establishing Application Security and Application Roles
  New Information - SQL Server 2000 SP3.

The security system in Microsoft® SQL ServerT is implemented at the lowest level: the database itself. This is the best method for controlling user activities regardless of the application used to communicate with SQL Server. However, sometimes security controls must be customized to accommodate the special requirements of an individual application, especially when dealing with complex databases and databases with large tables.

Additionally, you may want users to be restricted to accessing data only through a specific application (for example using SQL Query Analyzer or Microsoft Excel) or to be prevented from accessing data directly. Restricting user access in this way prohibits users from connecting to an instance of SQL Server using an application such as SQL Query Analyzer and executing a poorly written query, which can negatively affect the performance of the whole server. 

-- 
Keith
"Patman" <p_hoard@yahoo.com> wrote in message news:2a0255b0.0403301228.72bb7128@posting.google.com...
> I'm kind of new to SQL so if this question has been answered recently
> I apologize.
> 
> I have a login script that caputures user and computer info and writes
> it to a SQL db.  To avoid a login/password in my text logon script I
> using a trusted connection with "Domain users" having
> select/insert/update permissions in the db.  My problem is that any
> authenicated user can view this data from Access, SQL Enterprise
> Manager, etc.
> 
> Is is possible to restrit this db so that authenicated users can still
> select/write to the db but not be able to view from other ODBC related
> sources?
> 
> TIA,
> Pat

Relevant Pages

  • SQL Security
    ... I'm kind of new to SQL so if this question has been answered recently ... I have a login script that caputures user and computer info and writes ... select/insert/update permissions in the db. ... authenicated user can view this data from Access, ...
    (microsoft.public.sqlserver.server)
  • Parsing Domain Groups with .NET
    ... authenicated user is in when they login/navigate through ... get that info (Domain Admins and SQL DBA's) on the groups ...
    (microsoft.public.dotnet.security)
  • RE: SQL Security
    ... Use Windows authentication on SQL connection in login script. ... (Users cannot capture LOGIN NAME and PASSWORD from login script) ...
    (microsoft.public.sqlserver.server)