SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Capacity Planning SQL Server 2005


Capacity Planning SQL Server 2005

Author
Message
vkundar
vkundar
SSC Eights!
SSC Eights! (809 reputation)SSC Eights! (809 reputation)SSC Eights! (809 reputation)SSC Eights! (809 reputation)SSC Eights! (809 reputation)SSC Eights! (809 reputation)SSC Eights! (809 reputation)SSC Eights! (809 reputation)

Group: General Forum Members
Points: 809 Visits: 869
Hi,

We are planing to scale out our Database and if the number of users will increase to 5000 then what all the parameter I need to consider?
Right now 500 GB HDD & RAM 2 GB

Cheers,

Got an idea..share it !!

DBA_Vishal
Minaz Amin
Minaz Amin
SSCrazy
SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)

Group: General Forum Members
Points: 2676 Visits: 1750
You need to consider scaling up your processor, RAM, Netwrok Speed, Fast disk subsystem apart from DB load balancing. If number of users increase then start thinking for database load balancing, by configuring Database partitioned views , Shared server or Replication.

"More Green More Oxygen !! Plant a tree today"
curious_sqldba
curious_sqldba
SSCertifiable
SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)

Group: General Forum Members
Points: 7300 Visits: 3696
Minaz Amin (6/11/2009)
You need to consider scaling up your processor, RAM, Netwrok Speed, Fast disk subsystem apart from DB load balancing. If number of users increase then start thinking for database load balancing, by configuring Database partitioned views , Shared server or Replication.



There isn't db load balancing in sql world Sad
Evil Kraig F
Evil Kraig F
SSC-Insane
SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)SSC-Insane (20K reputation)

Group: General Forum Members
Points: 20301 Visits: 7660
sqldba_newbie (4/30/2012)
Minaz Amin (6/11/2009)
You need to consider scaling up your processor, RAM, Netwrok Speed, Fast disk subsystem apart from DB load balancing. If number of users increase then start thinking for database load balancing, by configuring Database partitioned views , Shared server or Replication.



There isn't db load balancing in sql world Sad


No, but you can fake it. IE: All read queries pull from replicated copies of the DB while you maintain the primary for DML only.

That said, however, 5000 users shouldn't really be a lot, but it depends on the use case of the database. I'm pretty sure the HP website (as a random example) handles a lot more than 5000 simultaneous users browsing their products.

If you're scaling the usage, you need to look at the current usage and determine if you have any existing bottlenecks or are close to hitting one. Then review the use case of the additional users and attempt to determine if they're going to affect those bottlenecks heavily.

This is one of those cases where I recommend you bring in an expert for a week or two to review your system and intended changes and get you a recommendation for a design path for your regular staff to review and implement. It's not a linear kind of thing, it all revolves around the nuances of the load increase.

EDIT: I just realized this was a 2 year old necro. Well, the OP won't care but anyone else who trips on it might.


- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions | Forum Netiquette
For index/tuning help, follow these directions. |Tally Tables

Twitter: @AnyWayDBA
curious_sqldba
curious_sqldba
SSCertifiable
SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)

Group: General Forum Members
Points: 7300 Visits: 3696
Evil Kraig F (4/30/2012)
sqldba_newbie (4/30/2012)
Minaz Amin (6/11/2009)
You need to consider scaling up your processor, RAM, Netwrok Speed, Fast disk subsystem apart from DB load balancing. If number of users increase then start thinking for database load balancing, by configuring Database partitioned views , Shared server or Replication.



There isn't db load balancing in sql world Sad


No, but you can fake it. IE: All read queries pull from replicated copies of the DB while you maintain the primary for DML only.

That said, however, 5000 users shouldn't really be a lot, but it depends on the use case of the database. I'm pretty sure the HP website (as a random example) handles a lot more than 5000 simultaneous users browsing their products.

If you're scaling the usage, you need to look at the current usage and determine if you have any existing bottlenecks or are close to hitting one. Then review the use case of the additional users and attempt to determine if they're going to affect those bottlenecks heavily.

This is one of those cases where I recommend you bring in an expert for a week or two to review your system and intended changes and get you a recommendation for a design path for your regular staff to review and implement. It's not a linear kind of thing, it all revolves around the nuances of the load increase.

EDIT: I just realized this was a 2 year old necro. Well, the OP won't care but anyone else who trips on it might.


Oh yeah makes sense now. We actually have a sort of similar scenario what you have, like all reads going to local-subscribers and writes to one-main- publisher...Works pretty good but we will eventually want to get rid of linked servers and may be use merge replication....ofcourse we still need to do lot of testing before we deploy in production.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search