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 |
|
JustinBigelow
SQL Gigolo
1157 Posts |
 Posted - 2001-07-31 : 00:04:00
|
Hey folks,I'd like to pick some brains  . I'm developing an app. This app will be used by multiple companies (hopefully) and each company will have its own database on the server. I have a stored proc that users execute to generate logins for their employees so they can make use of the app. Now for the login I'm using an EmployeeID that is generated by the customer company so it could be a social security number (for us yanks) or it could be an arbitrary number scheme desginated by the customer. If everybody used a social security number I would be ok since I'm pretty sure our gov't doesn't duplicate numbers. But... if CustomerA uses an arbitrary number to identify their employees and CustomerB does as well there is a possibility (albeit highly unlikely) that they will both try and create a login in the server with the same number. For example both have an employee with an employee id of 12345. CustomerA wouldn't have any problems but CustomerB would have to come up with a different number since 12345 already exists in syslogins. I'm toying with the idea of appending the databaseid number to the end of the login. Since each company will have their own database that should solve my problem. Is there an easier solution I'm overlooking? Looking the other way and hoping it doesn't come up is not an option I'm considering.Thanks,Justin |
|
|
|
|
|
SQL Server login question