What do you do when your website grows?

Hello,

We have an application developed in asp.net. We sell this application as a white label to insurance companies.

We launched this application about a month ago, and we already have about 12,000 accounts. There are several web servers (IIS) for the different white labels, and a big database server that supports all white labels.

We need to have everything on one database for reporting purposes.

We now got a new white label that wants to bring about 500,000 users, so I freaked out. My question is this, we handle prety well the web servers by adding a new server when it is necessary, but what about the SQL Server?

The database has about 140 tables, one of the tables grows at a rate of 1,000+ records per day with only 12K users, and Im scared cause I dont know how will I handle this in the future. Someone told me there's a way to split the tables among several SQL Servers, but Changing the SQL scripts on about 400 pages freaks me out.

What are the most best solutions or scenarios to handle this? I have a lab/test environment where I can start testing the solutions.

Thanks!
pvg1975Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Greg HejlPrincipal ConsultantCommented:
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Olaf DoschkeSoftware DeveloperCommented:
The one application I maintain with an SQL Server backend is not a website, and only has ~1000 users concurrent, but produces several 10 GB of transaction log a day, which is truncated, of course. The database itself does not grow that much.

1000+ records a day isn't much. But interpolating for 500,000 users you will expect 40,000 records a day in that table. That alone doesn't tell much, of course the size and typical transaction times matter. In the first place, monitor. SQL Server Profiler would help with that, or third party tools.

Methods of scaling are listed here:
http://www.scalesql.com/scaling-sql-server.aspx

Scaling out would not really be needed, but shows it can be done, as you can also add IIS webservers. In the first place, start with performance tuning, as you won't likely rewrite and adapt to a sharded database.

Bye, Olaf.
0
pvg1975Author Commented:
Thanks guys
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.