June 25, 2010 at 7:48 am
Performance will definitively not be an issue.
Having an user per application allows you to be more granular on permissions for each one, so that is actually not a bad practice.
If you need to turn of access to one application you would not affect the other ones for example.
June 25, 2010 at 10:59 am
Thanks for your response. Currently there are some blocking issues on DB server when they use single account. App team is saying if there are multiple account this will not happen, Is this true ? Is there any difference in database object/data accessing with multiple account vs single account?
----
AKP
June 25, 2010 at 11:04 am
blocking is not affected by users...it's affected by two connections selecting and updating the same row of at nearly the same time.
...whether it is two connections with the same user, or two connections with different users, the user is not what is affecting the blocking/contention, it's the accessing/updating of the data that is the issue.
I'd be running something like this to find out more about any blicking issues:
SELECT *
FROM sys.dm_exec_requests
WHERE wait_time > 0
AND blocking_session_id != 0
Lowell
June 25, 2010 at 12:41 pm
As Lowell mentioned, it makes no difference if you use different users when they touch the same tables.
I would actually look at the underlying code that causes the blocking. In most cases by rewriting it or using locking hints (if possible) it can be easily solved.
Viewing 4 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply