Help planning scale up/scale out

Hi there,
     Need some advice.  We're starting to outgrow the server that we're using for our datbase that is the back-end of a Cold Fusion website.  What's the best way to go?

One option is to just buy a bigger server and move the datbase to that one.

Other than that option, what is the deal with adding MORE (scale out) servers.  Is that datbase partitioning, or is that something else, and in a broad sense how does that work?  Does each server have a copy of SQL server installed on it, and each database would be different, containting different information? (I.E. one database contains a certain set of tables like customer data, and the other database contains other tables like order data).
I keep hearing about database partitioning, and can't figure out if that's what I'm looking at doing by using two different computers, or if that's called something else.
Also if I'm using to servers with databases on them to improve performance, does it matter if I use SQL server Enterprise or Standard?

Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

chapmandewConnect With a Mentor Commented:
There are a couple of ways to do it....
1.  Split your data onto different servers.  Each DB has the same set of tables, but only a subset of the overall data.
2.  Put certain tables on different servers.  Some servers have large tables, while other servers have others.
3.  A mixture of 1 & 2.  Either way, you are looking at distributed partiioned views to bring the data together.  Also, either way you're going to need some type of middleware software to know where to write/pull data.

4.  This is SQL 2005 specific, but you could use peer-to-peer replication.  All of the peers in the replcation set have the entire set of data.  When data chagnes at one node, it is propogated to the others.

Here is a neat article on how scaled itself out.

All Courses

From novice to tech pro — start learning today.