November 9, 2010 at 1:20 pm
Has anyone heard or witnessed severe or even a little performance degradation after creating multiple logins back to back during peak hours?
November 9, 2010 at 1:23 pm
Nope. I've done that, and never seen an issue. Unless by "multiple" you mean hundreds or thousands, which might eat a few too many resources.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
November 9, 2010 at 2:34 pm
Nope.
User creation may be one of the less intrusive activities I can think about.
In our shop we have to have an approved Change Ticket to touch production, only exceptions are user creation and password reset. Those changes shouldn't have any impact in overall performance.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.November 9, 2010 at 10:28 pm
I have not come across any performance issues because of creating SQL Logins back to back
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
November 10, 2010 at 9:33 am
never seen this. Creating logins should just touch some system tables in master (principals tables), nothing else. If you were creating lots, possibly you could block some connections checking against those tables, but those should be split-second locks to add data. Unless you were adding thousands of logins, I can't see this being an issue.
Or if you were doing this in a transaction and held it open, it could be an issue.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply