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 |
|
beachldy
Starting Member
3 Posts |
 Posted - 2011-11-07 : 10:48:37
|
| For years, our apps queried location data (Example: Office 1 in GA, Office 2 in FLA, Office 3 in UTAL) by reading the DOMAIN from an API call. We also used NT Groups as logins on SQL Server, and then in each database, used ROLES to which we added the logins to. When the user opened any of the apps, their domain would determine which location of records they could view/edit/update, and would filter the records that way so they only saw their location data.This will no longer be feasible as we are going to only have one domain for everyone. Does anyone have a better idea, than us making a USER TABLE with the location information in it? It would be a maintenance nightmare to maintain a user table with so many employees coming and going. |
|
|
|
|
|
Filtering Locations by Domain alternative?