I blogged a few years ago about my configuration tables for Ola Hallengren’s maintenance solution that allows me to pull the configuration parameters from tables so I don’t have to edit SQL Agent jobs and allows me to query tables to see how all my jobs are configured with Ola’s
As part of starting a new job, you need a way to get a good inventory of basic information about SQL Server instances. Once you have done what I outlined in this blog post. I find it helpful to run Glenn Alan Berry’s Diagnostic Notebooks against all the instances to
I mentioned in my New Database Job – The 90 Day Plan blog how I have a trick for storing index usage stats up until close to the next reboot of the SQL Server. You really can do this for any DMV-related query that you get reset at the reboot of
In my previous post, I expounded on the first 30 days I had at four jobs in the last four years. and how to set up your jobs box. I commented and got quoted on the fact that if it’s documented I don’t support it. So, these are methods of
Problem My company heavily uses MSX/TSX jobs for everything. But our SAN doesn’t necessarily like if we run all our index maintenance, backups, and integrity checks at the same time. So here is a quick little post on how you can schedule the workload to spread out across all your servers across
Problem For good database design, it is not idea to have everything in your PRIMARY filegroup so you can do partial backups, piecemeal restores, and for performance to separate your tables and indexes. You need different filegroups when looking at separating your indexes and tables and partitioning. Creating all these
UPDATE, April 18, 2017: Ola has added this functionality directly to his scripts. Please download his scripts instead as they have more error handling and other functionality built-in. I will be updating my configuration tables and procedures shortly. This is part 2 of 2 on taking smart backups. I wrote a previous
UPDATE, April 18, 2017: Ola has added this functionality directly to his scripts. Please download his scripts instead as they have more error handling and other functionality built-in. I will be updating my configuration tables and procedures shortly. This is part 1 of 2 part series on taking smart backups. Part 1
Problem Recently, I read an article on extended events where you can watch proportional fill happen on your files. It reminded of a process I wrote to solve a problem we had with page contention (PFS) with our systems processing upwards of 30K transactions per second. So I wrote a process
Problem The current environment is rather unique, with a unique workload that requires writing things like this. One of those being having the transactions cache on the server take up nearly 10 GBs of our memory. Being that we would like that 10 GBs of memory go towards the Buffer Pool