Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Concurrent Database Access Per Instance Expand / Collapse
Posted Tuesday, January 22, 2013 12:42 AM


Group: General Forum Members
Last Login: Monday, March 14, 2016 6:12 AM
Points: 113, Visits: 226
Hi All,

I am a newer in this forum. We are using SQL Server 2008 R2 Enterprise Edition in our Company. We are using single instance in our server. I have 500+ databases in my server.

Now my question is that how many user can access concurrent database per instance? Are 60+ database users can access this concurrently?

If not what will be the remedy?
Post #1409837
Posted Tuesday, January 22, 2013 1:09 AM



Group: General Forum Members
Last Login: Tuesday, July 19, 2016 4:34 AM
Points: 2,850, Visits: 4,076
i dont think there is any limitation of connections .SQL Server will handle large numbers of connections without a problem. A more important question is whether your database schema and application code will be able to handle it.

More users trying to access and modify the same data at the same time will likely lead to a lot more request blocking from all the table/row locking in the database. The performance of the app may slow to a crawl with that sort of usage. Without seeing your database schema, it's hard to tell. Although assuming you just did a simple conversion from Access to MS-SQL, it's likely you're not taking advantage of things a real RDBMS is good at like constraints, foreign keys, and indexing.

FYI SQL Server allows a maximum of 32,767 user connections.

I work only to learn Sql Server...though my company pays me for getting their stuff done
Post #1409846
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse