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 |
|
blindman
Master Smack Fu Yak Hacker
2365 Posts |
 Posted - 2008-07-28 : 09:47:57
|
| What is the largest number of users you have had on a single database?What is the largest number of users you have accomodated using individual SQL Server authentications?What is the largest number of users you have accomodated using individual Windows Authentication logins?Have you ever "rolled you own" application security within a database, and how many users did you accommodate?What were the administrative problems you experienced using any of these alternatives?e4 d5 xd5 Nf6 |
|
|
blindman
Master Smack Fu Yak Hacker
2365 Posts |
Posted - 2008-07-29 : 01:15:06
|
| Aw, c'mon guys and gals. Isn't it bad enough that more forum is down without getting the silent treatment here?e4 d5 xd5 Nf6 |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2008-07-29 : 04:49:06
|
| we have aroud 1000 users in our own login table that hadles security for the apps.each app uses it's own sql auth to connect to sql server, there are around 6 apps.this way moving logins isn't a problem at all.direct db access is also done with win auth._______________________________________________Causing trouble since 1980Blog: http://weblogs.sqlteam.com/mladenpSpeed up SSMS development: www.ssmstoolspack.com <- version 1.0 out! |
|
|
|
blindman
Master Smack Fu Yak Hacker
2365 Posts |
Posted - 2008-07-29 : 09:39:19
|
| Excellent!I'm thinking of a web-based app, so Windows authentication for users would not be possible.I've rolled my own row-level security before in an EDI database. Each user logged in with a password and received a temporary token (GUID) once the password was validated. Thereafter, this token was passed as a parameter to every procedure, which verified that the token was valid and up-to-date before processing the request.It worked, but it was clunky having to pass and verify the token in every procedure, and it seems superfluous if I can give each user their own SQL Server login and manage those effectively. I've just never managed hundreds or thousands of SQL Server logins so I have no idea what kind of drawback there might be.e4 d5 xd5 Nf6 |
|
|
|
LoztInSpace
Aged Yak Warrior
940 Posts |
Posted - 2008-07-31 : 10:25:15
|
| >1 million users via several (around 100) service accounts for various web apps. One database supports all the user profiles and large chunks of web content. Once you're in then you are in so I've never done the per-enquiry thing. Never done the row level stuff at the user level, it has always been restricted to various functions via roles in the app. |
|
|
|
|
|
|
|
|
Largest number of users you have accomodated?