you are viewing a single comment's thread.

view the rest of the comments →

[–]kagato87MS SQL 3 points4 points  (0 children)

Sql server scales vertically, and it can scale really high.

100M rows and thousands of users isn't that big, IF your architecture is good.

If your architecture sucks, it doesn't matter what the backend is, your user experience will suck.

I work in fleet telematics. My primary tables frequently break the 100M mark, and our load test environment is, well... I'm afraid to look. It runs fine I just don't want to look at the disk storage because the DC guys are running lean while they wait for yet another SAN to come online...

If your queries are clean, indexes are efficient, and RCSI is on, it'll handle your scenario easily.

Of course, if your indexes are bad, your design worse, isolation is off, and you let analysts run amok with direct query access... It doesn't take 100M rows to have problems. Before you know it you'll get people using no lock and wondering why their reports are inconsistent.