• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 393
  • Last Modified:

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!
0
pvg1975
Asked:
pvg1975
2 Solutions
 
Greg HejlPrincipal ConsultantCommented:
0
 
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

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now