Last night we had a major release that involved a massive data dump and some complex queries. We semi-anticipated the slowness and were able to react quickly to creating some new indexes in SQL Server 2012. However, the site was lagging for quite a long time post-release.
Is there a way to manage and prevent this ahead of time? You can't create indexes before the data is on the production database, but there must be some way to prepare the database.
Part of the problem is not just indexes, but giving the database enough time to get statistics to make the indexes more efficient.
One thought I had was it might have something to do with sharding or replication, or perhaps some sort of db merge.