 |
Experts on Demand
Using Windows NT and SQL Server, what is the best way to add security by using both authentication in Windows NT and then authorization in SQL Server? And what is the best way to have record-level security for SQL tables? Is there any information on how to build Windows NT and SQL Server security using DLLs? Or is that something I would want to do?
QUESTION POSED ON: 23 AUG 2005
QUESTION ANSWERED BY: Kevin Kline
I personally prefer SQL Server authentication over Windows authentication for what you are trying to do, though at the end of the day either will do just as well. In SQL Server 2000, most shops that want to use row-level security implement it by granting the users access only to views or stored procedures that then provide access to the underlying tables. Building your own custom security DLLs sounds like way too much work to me. I suggest you spend some time on the SQLSecurity Web site for the industry's best information on locking down and securing SQL Server.
|
|
|
|
|
|
|
|
| TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of . |
|
| |
All Rights Reserved, , TechTarget |
|
|
|
|
|
