Blog do Ezequiel
  SQL Server Insights


July, 2011

Latest Updates
06/02/2015 - Latest update on the AdaptiveIndexDefrag procedure v1.6.1. Look for it in the "Ezequiel shortcuts" section on the right or just click HERE.

11/03/2015 - Updates to Maintenance plan deployment scripts available HERE

17/05/2015 - The SQL Swiss Army Knife Series Index
  • Blog do Ezequiel

    What's new in Performance Point Services (SharePoint 2010 SP1)

    Hi, In the continuation of our Business Intelligence series in our Ezequiel Blog, I’m making this post to announce the release of SharePoint 2010 SP1 and the new features that have been included. From a BI perspective there are several functionalities...
  • Blog do Ezequiel

    SQL Swiss Army Knife #10 - VLFs again. What’s your current status?

    EDIT (11-01-2011): A parenthesis was missing making the log_size_MB value skewed. Thanks Luis! EDIT (26-03-2012): Updated script for SQL 2012 support. EDIT (19-11-2012): Added information from Fixing VLFs post , namely potential log size after fix...
  • Blog do Ezequiel

    Notes about SQL Server 2008 R2 SP1

    Hi, The purpose of this post is to share some notes (links) about the recent release of SQL Server 2008 R2 SP1: SQL Server 2008 R2 SP1 Technorati Tags: SQL Server 2008 R2 SP1 , Service Pack Download
  • Blog do Ezequiel

    MOSS, BizTalk, SCOM and SQL Server Collations

    Hello all, The topic today is database and server collations. As part of pre-installation tasks for SQL Server, we should always take into account what is the collation required by the user databases. Why is that? Collation is a subject many times...
  • Blog do Ezequiel

    Adaptive Index Defrag


    The purpose for this procedure to to perform an intelligent defrag on one or more indexes for one or more databases. The 1st release was inspired by an earlier release of Michelle Ufford’s code in site, and has since evolved to suit different and added needs. In a nutshell, this procedure automatically chooses whether to rebuild or reorganize an index according to its fragmentation level, amongst other parameters, like if page locks are allowed or the existence of LOBs.
    All within a specified time frame you choose, defaulting to 8 hours. The defrag priority can also be set, either on size, fragmentation level or index usage (based on range scan count), which is the default.
    It also handles partitioned indexes, optional statistics update (table-wide or only those related to indexes), rebuilding with the original fill factor or index padding and online operations, to name a few options.

Page 1 of 1 (5 items)