how do you handle huge databases?

Geeks With Blogs

The Wrecking Bawl Destructuring query language, one keyword at a time.

<< so long Max | Home | a couple great quotes >>

I'm used to working with SQL Server databases that are somewhat small (10 GB or less, usually a lot less), so I'm curious how people deal with huge databases, like those that hold Amazon's transactions or whatever. Do you have to have the latest and greatest hardware running with clustered servers? Do you have to do a lot of database partitioning? How do you handle upgrades? Do you do then in the middle of the night so that you can take the db down briefly? Posted on Wednesday, August 22, 2007 4:55 AM all tech stuff , SQL Server | Back to top

Comments on this post: how do you handle huge databases?

# re: how do you handle huge databases?

Normally these are done with clustered servers for hardware to due with redundancy, sans for storage planning, clustered databases and load balancers for performances and partitioning for housekeeping. There're normally failovers as well to ensure 0 downtime.

Left by Nestor on Aug 22, 2007 6:02 AM

Your comment:

Title:

Name:

Email: (never displayed) (will show your gravatar)

Comment: Allowed tags: blockquote, a, strong, em, p, u, strike, super, sub, code

Verification:

Code Monkey Projectiles - Index

ASP.Net SQL Server Apple Google SharePoint Windows Visual Studio Team Foundation Server Agile Office Design Patterns Web Azure