Black Friday prices end in 8d 14h 37m — See the sale

Category: Clients and Case Studies

Production DBA

How Many Databases Can I Put on One SQL Server?

I've seen servers with thousands of databases on a single SQL Server, and it works. Sure, opening the databases list in SQL Server Management Studio is painful, and a lot of third party monitoring tools fall over, but it's not so bad once you know how to work around these issues.

But there's two issues you can't work around: our old archenemies, RPO and RTO. A quick reminder:

Read more about How Many Databases Can I Put on One SQL Server? 22 comments — Join the discussion

Announcing kCura Relativity 9, Data Grid, Elasticsearch, and SQL Server

Today at Relativity Fest in Chicago, kCura Relativity 9 introduces the option to move some text storage out of Microsoft SQL Server and into kCura's new Data Grid, a tool built atop the open source Elasticsearch. Is kCura abandoning SQL Server? No, but understanding what's going on will help you be a better database administrator and developer.…

Read more about Announcing kCura Relativity 9, Data Grid, Elasticsearch, and SQL Server 4 comments — Join the discussion

Tiering kCura Relativity Databases (Or Any SaaS Product)

When you're the database administrator working with a software product that stores every client's data in a different database, the sheer number of databases can be intimidating. As you grow from dozens to hundreds to thousands of databases, you can't treat all of them equally.

Start by making a graph of the database sizes - here's an example from one of my clients with 58 databases on a server (certainly not a big number, but just easy to digest in a blog post):

Read more about Tiering kCura Relativity Databases (Or Any SaaS Product) 9 comments — Join the discussion

How to Use Partitioning to Make kCura Relativity Faster

kCura Relativity is an e-discovery program used by law firms to find evidence quickly. I've blogged about performance tuning Relativity, and today I'm going to go a little deeper to explain why DBAs have to be aware of Relativity database contents.

In Relativity, every workspace (case) lives in its own SQL Server database. That one database houses:

Read more about How to Use Partitioning to Make kCura Relativity Faster 4 comments — Join the discussion

Update on Stack Overflow’s Recovery Strategy with SQL Server 2014

Back in 2009 (wow, seems like only yesterday!), I wrote about designing a recovery strategy for Stack Overflow. Back then, I wrote: With these answers in mind, Stack Overflow’s decisions not to do transaction log backups, offsite log shipping, database mirroring, and so on make good business sense. Us geeks in the crowd may not like it,…

Read more about Update on Stack Overflow’s Recovery Strategy with SQL Server 2014 2 comments — Join the discussion

Microsoft SQL Server 2012 Always On AGs at StackOverflow

I recently finished helping the StackExchange team migrate their SQL Server 2008 infrastructure to SQL Server 2012. These servers power StackOverflow, DBA.StackExchange.com, the new AskPatents partnership with the US Patent and Trademark Office, and hundreds of other Q&A sites that together form one of the biggest web site networks. It's one of the most visible…

Read more about Microsoft SQL Server 2012 Always On AGs at StackOverflow 25 comments — Join the discussion
Production DBA

How to REALLY Compress Your SQL Server Backups

StackOverflow's database servers are hosted in a colo facility. They pay by the byte for transfer in and out of their servers, so it's really crucial to compress the database backups as much as possible. The smaller the backups, the less they pay. They're already using backup compression, but they wanted to explore more ways to cut their backup sizes.

Read more about How to REALLY Compress Your SQL Server Backups 45 comments — Join the discussion
Production DBA

Designing a Recovery Strategy for StackOverflow

When I design a backup & recovery strategy for a database, I don't talk to the developers, database administrators, or systems administrators first.  The first people I go to are the business managers, and I ask three questions:

How much money would you lose if you lost the data altogether?
How much money would you lose if you were down for X hours?
How much time & money can you afford to devote to backups?

Read more about Designing a Recovery Strategy for StackOverflow 11 comments — Join the discussion