SQL Swiss Army Knife Series is indexed

[Pedro Lopes]

First published on MSDN on Feb 19, 2013
Hello all,

By popular demand, I’m creating this post to serve as the central location for all past and future posts of the “SQL Swiss Army Knife” series, which should also make it easier to find and new updates.

Tag	Script	Initial Release	Latest Update
Securables	#1 - Scripting Securables	26 Apr 2010	18 Nov 2016
Logins	#2.1 - Scripting Logins	21 Jun 2010	18 Mar 2013
I/O	#3 - View I/O per file	21 Oct 2010	8 Mar 2012
Filestream	#4 - Making sense of FILESTREAM containers	02 Nov 2010	-
Autogrow	#5 - Checking Autogrow times	16 Nov 2010	28 Feb 2013
DB Compression	#6 - Evaluating compression gains	03 Jan 2011	03 Dec 2013
Indexing	#7 - Adaptive Index Defrag	10 Mar 2010	Check here
Maintenance	#8 - Find a Maintenance Window	22 Mar 2011	-
VLF	#9 - Fixing VLFs	24 May 2011	20 Sep 2012
VLF	#10 - VLFs again. What’s your current status?	21 Jul 2011	19 Nov 2012
Workload	#11.1 - Locking, blocking and active transactions	03 Oct 2011	2 Dec 2016
Indexing	#12 - Index information galore!	7 Apr 2012	3 Nov 2016
Plan Cache	#13 - Exploring the plan cache – Part 1	01 Aug 2013	16 Mar 2014
Plan Cache	#13 - Exploring the plan cache – Part 2	16 Mar 2014	15 Apr 2014
Waits / Latches	#14 - Troubleshooting with Waits and Latches	13 Apr 2014	12 Apr 2017
Indexes	#15 - Handling duplicate indexes	12 Nov 2014	-
Plan Cache	#16 - Too many single use plans, now what?	30 Jul 2014	-

Hope you find it useful!

Disclaimer: I hope that the information on these pages is valuable to you. Your use of the information contained in these pages, however, is at your sole risk. All information on these pages is provided "as -is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Ezequiel. Further, Ezequiel shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.