And to alleviate the problem temporarily we needed to bounce the instance and clear up the temp database files. But luckily there is a patch. More information provided in this article. We also needed to disable the Read Committed Snapshot Isolation Level in order to keep the growth under control. More information about it this …
Better hardware and the latest SQL Server release does not always mean that things will run faster.
Allowing me to sleep properly and investing time on number crunching.
So what is happening next year? Many exiting things, with a core focus on HA, DR, Analytics, SharePoint 2010, and VMware on production databases
We executed the migration of stand-alone database servers to an active/active cluster. This was for our enterprise-wide reporting solution which includes a scaled-out deployment of Reporting Services implementing F5 BIGIP as a load balancer.