Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
prussell
Starting Member
1 Post |
 Posted - 2005-02-23 : 10:29:08
|
| I am upsizing an application from access to SQL Server 2K. The app uses a user table for app login and an app access table for users access levels to the app itself. We have probably 200 users, and 5 different access levels. What is the best way to tie logged in users to the login, and then users and roles on the database? I want to use the same login for the ado connection...something like APPUser. How do i then differenciate each user for the various access levels?Tahnk for your helpPatrick |
|
|
clarkbaker1964
Constraint Violating Yak Guru
428 Posts |
Posted - 2005-02-23 : 13:27:56
|
If your front end security model is table based you will need to recreate those tables. You could take one of two approaches to the sql side. Create an application account and let the front end handle the rest. Create NT accounts for all 200 users. Which would be transparent to the user logging in preferred method.Create Groups that represent functionality assign the permissions to these groups (read/update/etc), then assign the users to these groups.Depending on your approach and the nature of your security model ie (functionality versus sensitivity) their are many more choices to make. You can do anything at www.zombo.com |
 |
|
|
|
|
|
Logins Users and Roles