Converting to Windows Authentication
From: CurtM (cndmoyer_at_hotmail.com)
Date: 10/02/03
- Next message: Sue Hoegemeier: "Re: Encrypting credit card numbers columns in SQL Server"
- Previous message: Richard Waymire [MSFT]: "Re: DRI?"
- Next in thread: Cindy Gross: "RE: Converting to Windows Authentication"
- Reply: Cindy Gross: "RE: Converting to Windows Authentication"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 2 Oct 2003 10:34:38 -0700
I've got about ten Windows 2000 Sql servers that I am
trying to convert from sql server security to windows
authentication. There are currently two sql server logins
that generally have the following database-level
permissions on these sql servers:
Login1: Datareader, Create Procedure
Login2: Datareader, Datawriter, Create Procedure, Create
Table
We have about a dozen client workstation-type machines
that access the Sql Servers and run a variety of VB jobs
that hit the sql servers. These jobs run semi-randomly
and depending on the job may use login1 or login2. In
other words, any given client machine uses both logins
throughout the day to hit the same server/database
combinations.
That leads to my question: how can I convert to windows
authentication when a trusted connection will always use
the network login of the machine and the corresponding
permissions that I have assigned to it in sql server? It
doesn't seem that I have the control that I do with sql
server logins to have different permission levels coming
from the same machine?
I would appreciate any ideas...
- Next message: Sue Hoegemeier: "Re: Encrypting credit card numbers columns in SQL Server"
- Previous message: Richard Waymire [MSFT]: "Re: DRI?"
- Next in thread: Cindy Gross: "RE: Converting to Windows Authentication"
- Reply: Cindy Gross: "RE: Converting to Windows Authentication"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
