Small database with 1 million users

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Administering » Small database with 1 million users

21 posts, Page 1 of 3

1 2 3 »»»

Small database with 1 million users

Rate Topic

Display Mode

Topic Options

Author

Message

Sqlsavy

Posted Monday, October 15, 2012 7:39 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 9:04 AM
Points: 194, Visits: 636

Hi all,

We've a small database (1 GB) and SQL 2005 server is clustered one. Now Business is forecasting that database will be accessed by million users by early next year.

Currently there are only 300 users using the database .

How to plan the resources for such a massive requirement?

Any help would be appreciated

Thanks in advance

Cheers

Post #1372726

durai nagarajan

Posted Monday, October 15, 2012 7:43 AM

SSC Eights!

Group: General Forum Members
Last Login: Yesterday @ 10:16 AM
Points: 863, Visits: 2,135

what about windows group access if it requires only same level of access..

Regards
Durai Nagarajan

Post #1372729

Sqlsavy

Posted Monday, October 15, 2012 7:47 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 9:04 AM
Points: 194, Visits: 636

Thanks for your response but i am not worried about giving access through AD group.

My question is how much CPU, Disk etc is required so that users can access the database without any bottlenecks

Post #1372732

vyas

Posted Monday, October 15, 2012 7:52 AM

Hall of Fame

Group: General Forum Members
Last Login: Thursday, May 16, 2013 4:02 AM
Points: 3,131, Visits: 1,056

What is the server meant for ? Reporting or transactions? What is the budget ?

Post #1372737

durai nagarajan

Posted Monday, October 15, 2012 7:58 AM

SSC Eights!

Group: General Forum Members
Last Login: Yesterday @ 10:16 AM
Points: 863, Visits: 2,135

but i am not worried about giving access through AD group.

what is the thing you are worried about?

Regards
Durai Nagarajan

Post #1372738

Sqlsavy

Posted Monday, October 15, 2012 7:59 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 9:04 AM
Points: 194, Visits: 636

This is a archived database and data is viewed via a managed solution. Budget is not an issue

Post #1372740

Bhuvnesh

Posted Tuesday, October 16, 2012 5:44 AM

SSCrazy

Group: General Forum Members
Last Login: Thursday, June 13, 2013 7:03 AM
Points: 2,562, Visits: 3,453

..

-------Bhuvnesh----------
While 1 = 1 (Learning SQL....)
Click to get fast response of your post

Post #1373164

Bhuvnesh

Posted Tuesday, October 16, 2012 5:45 AM

SSCrazy

Group: General Forum Members
Last Login: Thursday, June 13, 2013 7:03 AM
Points: 2,562, Visits: 3,453

Sqlsavy (10/15/2012)

How to plan the resources for such a massive requirement?

there is not any hard and fast rule for hardware upgradation , it depends on variuos factors like

no of concurrent users (in future)
Disaster recovery plan
data growth
how will you handle reports (same or different server ) in future
disk management
AND how much rich or complex application would be in future from resource comsumption point of view
etc etc

-------Bhuvnesh----------
While 1 = 1 (Learning SQL....)
Click to get fast response of your post

Post #1373165

Sqlsavy

Posted Tuesday, October 16, 2012 6:31 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 9:04 AM
Points: 194, Visits: 636

Thanks!

Post #1373195

TheSQLGuru

Posted Tuesday, October 16, 2012 7:17 AM

Hall of Fame

Group: General Forum Members
Last Login: Today @ 8:47 PM
Points: 3,673, Visits: 5,173

Sqlsavy (10/15/2012)

There are MANY factors that come into play when trying to get SQL Server to the extremes of scale. And they aren't all inside SQL Server or the Windows server itself either. Application connection pooling, network latency/bandwidth are two that come to mind outside the server. Networking stack configuration on the server will be key. Inside SQL, wow - the list of things that could be a bottleneck or may need to be tweaked is long, everything from latching issues to minimum memory per query.

You REALLY need to get an expert consultant involved sooner rather than later. You need a VERY VERY THOROUGH scalability testing plan, because I GUARANTEE you that you will run into things that will need to be dealt with. For example, I think you will need to avoid having a different login per user too - the login validation and security/access overhead would be overwhelming I think.

Honestly my gut says SQL Server cannot do 1M concurrent users on access regardless of hardware capabilities. I imagine you will need to have a scale-out approach if you need any reasonable fraction of those 1M users connected at the same time. Of course there is (currently) no version of SQL Server that can do this out of the box, so you will need to be creative.

In any case, best of luck with it, and please keep us apprised of your activities and how things go. I have helped some clients over the years get to extreme scale on SQL Server (7400+ databases on one server for example), and it is always interesting!! BTW, I would LOVE to help you try to get this to work. Cool

Best,

Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru at GMail

Post #1373232

« Prev Topic | Next Topic »

21 posts, Page 1 of 3

1 2 3 »»»

Permissions