This T-SQL Tuesday is brought to us by Arun Sirpal (b | t) and wants to write about a technical challenge we have conquered. Having been a DBA for 18 years now it’s hard to pick on a technical challenge but I will stick to the more recent challenge of
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
The Problem You have tables that have a lot of data inserted into them and deleted that use identity values and run out integers to use. I have over 3000+ databases where this can occur so we have an alerts setup that checks the tables then checks a table to
The Problem Our databases autogrow because we have thousands of databases and before we know we have databases with high VLF counts in the transaction logs. If you don’t know why that is bad refer to the resources section of this article. Update – November 5, 2017 I have added
This month Rob Sewell (Twitter | Blog) is hosting T-SQL Tuesday and wants us to automate more with PowerShell or at least learn PowerShell. My favorite thing to automate using PowerShell is checking on the status of things on multiple servers. For example, after patching your environment running a quick
Note: Since I wrote this dbatools had come out with an easier approach that you should check out here. Our Problem In a shared in environment you may have hundreds of databases with the same schema but depending on the data loaded into them not all of them will benefit
Introduction There is a lot of talk about what fill factor should be set for an index. We know for indexes that are ever increasing the fill factor should be set to 100% but for those indexes that are on things like last name or birthday it gets a bit
As part of upgrading our SQL Servers to 2017 CTP 2.1 we have a process that runs afterwards that uses Invoke-Sqlcmd cmdlet but with SQL Server 2017, SQL Server PowerShell 2017 is a separate install from the PowerShell Gallery. So I wrote a process to that will install the SQL