Wednesday, April 4, 2012

SQL Server Index and Statistics Maintenance

Just attended Orlando.Net Code Camp this past weekend and set in on a session from Rob Biddle a Data Architect where he had a recommended a Ola Hallengren index and stats maintenance process. Just wrapping up testing on the dev box now and slowly folding them into my production maintenance routine. Something you should check out.

Resource Link:
http://ola.hallengren.com/sql-server-index-and-statistics-maintenance.html


IndexOptimize is the SQL Server Maintenance Solution’s stored procedure for rebuilding and reorganizing indexes and updating statistics. IndexOptimize is supported on SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012.

Download

Download MaintenanceSolution.sql. This script creates all the objects and jobs that you need. You can also download the objects as separate scripts.

License

The SQL Server Maintenance Solution is free.

Support

Request professional support or custom modifications.

Parameters


Databases

Select databases. The keywords SYSTEM_DATABASES, USER_DATABASES, and ALL_DATABASES are supported. The hyphen character (-) is used to exclude databases, and the percent character (%) is used for wildcard selection. All of these operations can be combined by using the comma (,).
ValueDescription
SYSTEM_DATABASESAll system databases (master, msdb, and model)
USER_DATABASESAll user databases
ALL_DATABASESAll databases
Db1The database Db1
Db1, Db2The databases Db1 and Db2
USER_DATABASES, -Db1All user databases, except Db1
%Db%All databases that have “Db” in the name
%Db%, -Db1All databases that have “Db” in the name, except Db1
ALL_DATABASES, -%Db%All databases that do not have “Db” in the name

FragmentationLow

Specify index maintenance operations to be performed on a low-fragmented index.
ValueDescription
INDEX_REBUILD_ONLINERebuild index online.
INDEX_REBUILD_OFFLINERebuild index offline.
INDEX_REORGANIZEReorganize index.
INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINERebuild index online. Rebuild index offline if online rebuilding is not supported on an index.
INDEX_REBUILD_ONLINE,INDEX_REORGANIZERebuild index online. Reorganize index if online rebuilding is not supported on an index.
INDEX_REORGANIZE,INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINEReorganize index. Rebuild index online if reorganizing is not supported on an index. Rebuild index offline if reorganizing and online rebuilding are not supported on an index.
NULLDo not perform index maintenance. This is the default for a low-fragmented index.
An online index rebuild or an index reorganization is not always possible. Because of this, you can specify multiple index-maintenance operations for each fragmentation group. These operations are prioritized from left to right: If the first operation is supported for the index, then that operation is used; if the first operation is not supported, then the second operation is used (if supported), and so on. If none of the specified operations are supported for an index, then that index is not maintained.
IndexOptimize uses the SQL Server ALTER INDEX command: REBUILD WITH (ONLINE = ON) to rebuild indexes online, REBUILD WITH (ONLINE = OFF) to rebuild indexes offline, and REORGANIZE to reorganize indexes.

FragmentationMedium

Specify index maintenance operations to be performed on a medium-fragmented index.
ValueDescription
INDEX_REBUILD_ONLINERebuild index online.
INDEX_REBUILD_OFFLINERebuild index offline.
INDEX_REORGANIZEReorganize index.
INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINERebuild index online. Rebuild index offline if online rebuilding is not supported on an index.
INDEX_REBUILD_ONLINE,INDEX_REORGANIZERebuild index online. Reorganize index if online rebuilding is not supported on an index.
INDEX_REORGANIZE,INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINEReorganize index. Rebuild index online if reorganizing is not supported on an index. Rebuild index offline if reorganizing and online rebuilding are not supported on an index. This is the default for a medium-fragmented index.
NULLDo not perform index maintenance.
An online index rebuild or an index reorganization is not always possible. Because of this, you can specify multiple index-maintenance operations for each fragmentation group. These operations are prioritized from left to right: If the first operation is supported for the index, then that operation is used; if the first operation is not supported, then the second operation is used (if supported), and so on. If none of the specified operations are supported for an index, then that index is not maintained.
IndexOptimize uses the SQL Server ALTER INDEX command: REBUILD WITH (ONLINE = ON) to rebuild indexes online, REBUILD WITH (ONLINE = OFF) to rebuild indexes offline, and REORGANIZE to reorganize indexes.

FragmentationHigh

Specify index maintenance operations to be performed on a high-fragmented index.
ValueDescription
INDEX_REBUILD_ONLINERebuild index online.
INDEX_REBUILD_OFFLINERebuild index offline.
INDEX_REORGANIZEReorganize index.
INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINERebuild index online. Rebuild index offline if online rebuilding is not supported on an index.
This is the default for a high-fragmented index.
INDEX_REBUILD_ONLINE,INDEX_REORGANIZERebuild index online. Reorganize index if online rebuilding is not supported on an index.
INDEX_REORGANIZE,INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINEReorganize index. Rebuild index online if reorganizing is not supported on an index. Rebuild index offline if reorganizing and online rebuilding are not supported on an index.
NULLDo not perform index maintenance.
An online index rebuild or an index reorganization is not always possible. Because of this, you can specify multiple index-maintenance operations for each fragmentation group. These operations are prioritized from left to right: If the first operation is supported for the index, then that operation is used; if the first operation is not supported, then the second operation is used (if supported), and so on. If none of the specified operations are supported for an index, then that index is not maintained.
IndexOptimize uses the SQL Server ALTER INDEX command: REBUILD WITH (ONLINE = ON) to rebuild indexes online, REBUILD WITH (ONLINE = OFF) to rebuild indexes offline, and REORGANIZE to reorganize indexes.

FragmentationLevel1

Set the lower limit, as a percentage, for medium fragmentation. The default is 5 percent. This is based on Microsoft’s recommendation in Books Online.
IndexOptimize checks avg_fragmentation_in_percent in sys.dm_db_index_physical_stats to determine the fragmentation.

FragmentationLevel2

Set the lower limit, as a percentage, for high fragmentation. The default is 30 percent. This is based on Microsoft’s recommendation in Books Online.
IndexOptimize checks avg_fragmentation_in_percent in sys.dm_db_index_physical_stats to determine the fragmentation.

PageCountLevel

Set a size, in pages; indexes with fewer pages are skipped for index maintenance. The default is 1000 pages. This is based on Microsoft’s recommendation in this white paper.
IndexOptimize checks page_count in sys.dm_db_index_physical_stats to determine the size of the index.

SortInTempdb

Use tempdb for sort operations when rebuilding indexes.
ValueDescription
YUse tempdb for sort operations when rebuilding indexes.
NDo not use tempdb for sort operations when rebuilding indexes. This is the default.
The SortInTempdb option in IndexOptimize uses the SORT_IN_TEMPDB option in the SQL Server ALTER INDEX command.

MaxDOP

Specify the number of CPUs to use when rebuilding indexes. If this number is not specified, the global maximum degree of parallelism is used.
The MaxDOP option in IndexOptimize uses the MAXDOP option in the SQL Server ALTER INDEX command.

FillFactor

Indicate, as a percentage, how full the pages should be made when rebuilding indexes. If a percentage is not specified, the fill factor in sys.indexes is used.
The FillFactor option in IndexOptimize uses the FILLFACTOR option in the SQL Server ALTER INDEX command.

PadIndex

Apply the percentage of free space that the FillFactor parameter specifies to the intermediate-level pages of the index.
ValueDescription
YApply the percentage of free space that the FillFactor parameter specifies to the intermediate-level pages of the index.
NThe intermediate-level pages of the index are filled to near capacity. This is the default.
The PadIndex option in IndexOptimize uses the PADINDEX option in the SQL Server ALTER INDEX command.

LOBCompaction

Compact pages that contain large object (LOB) columns, when reorganizing indexes.
ValueDescription
YCompact pages that contain LOB columns, when reorganizing indexes. This is the default.
NDo not compact pages that contain LOB columns, when reorganizing indexes.
The LOBCompaction option in IndexOptimize uses the LOB_COMPACTION option in the SQL Server ALTER INDEX command.

UpdateStatistics

Update statistics.
ValueDescription
ALLUpdate index and column statistics.
INDEXUpdate index statistics.
COLUMNSUpdate column statistics.
NULLDo not perform statistics maintenance. This is the default.
IndexOptimize uses the SQL Server UPDATE STATISTICS command to update statistics.

StatisticsSample

Indicate, as a percentage, how much of a table is gathered when updating statistics. A value of 100 is equivalent to a full scan. If no value is specified, then SQL Server automatically computes the required sample.
The StatisticsSample option in IndexOptimize uses the SAMPLE and FULLSCAN options in the SQL Server UPDATE STATISTICS command.

StatisticsResample

Update statistics with the most recent sample.
ValueDescription
YUpdate statistics with the most recent sample.
NLet SQL Server automatically compute the required sample. This is the default.
The StatisticsResample option in IndexOptimize uses the RESAMPLE option in the SQL Server UPDATE STATISTICS command.
You cannot combine the options StatisticsSample and StatisticsResample.

OnlyModifiedStatistics

Update statistics only if any rows have been modified since the most recent statistics update.
ValueDescription
YUpdate statistics only if any rows have been modified since the most recent statistics update.
NUpdate statistics regardless of whether any rows have been modified.
IndexOptimize checks rowmodctr in sys.sysindexes to determine whether any rows have been modified since the most recent statistics update.

PartitionLevel

Maintain partitioned indexes on the partition level. If this parameter is set to Y, the fragmentation level and page count is checked for each partition. The appropriate index maintenance (rebuild or reorganize) is then performed for each partition.
ValueDescription
YMaintain partitioned indexes on the partition level.
NMaintain partitioned indexes on the index level. This is the default.

TimeLimit

Set the time, in seconds, after which no commands are executed. By default, the time is not limited.

Indexes

Select indexes. If this parameter is not specified, all indexes are selected. The ALL_INDEXES keyword is supported. The hyphen character (-) is used to exclude indexes, and the percent character (%) is used for wildcard selection. All these operations can be combined by using the comma (,).
ValueDescription
ALL_INDEXESAll indexes
Db1.Schema1.Tbl1.Idx1The index Idx1 on the object Schema1.Tbl1 in the database Db1
Db1.Schema1.Tbl1.Idx1, Db2.Schema2.Tbl2.Idx2The index Idx1 on the object Schema1.Tbl1 in the database Db1 and the index Idx2 on the object Schema2.Tbl2 in the database Db2
Db1.Schema1.Tbl1All indexes on the object Schema1.Tbl1 in the database Db1
Db1.Schema1.Tbl1, Db2.Schema2.Tbl2All indexes on the object Schema1.Tbl1 in the database Db1 and all indexes on the object Schema2.Tbl2 in the database Db2
Db1.Schema1.%All indexes in the schema Schema1 in the database Db1
%.Schema1.%All indexes in the schema Schema1 in all databases
ALL_INDEXES, -Db1.Schema1.Tbl1.Idx1All indexes except the index Idx1 on the object Schema1.Tbl1 in the database Db1
ALL_INDEXES, -Db1.Schema1.Tbl1All indexes except indexes on the object Schema1.Tbl1 in the database Db1

Delay

Set the delay, in seconds, between index commands. By default, there is no delay.

LogToTable

Log commands to the table dbo.CommandLog.
ValueDescription
YLog commands to the table.
NDo not log commands to the table. This is the default.

Execute

Execute commands. By default, the commands are executed normally. If this parameter is set to N, then the commands are printed only.
ValueDescription
YExecute commands. This is the default.
NOnly print commands.

Examples

A. Rebuild or reorganize indexes with fragmentation on all user databases

EXECUTE dbo.IndexOptimize @Databases = 'USER_DATABASES',
@FragmentationLow = NULL,
@FragmentationMedium = 'INDEX_REORGANIZE,INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE',
@FragmentationHigh = 'INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE',
@FragmentationLevel1 = 5,
@FragmentationLevel2 = 30

B. Rebuild or reorganize indexes with fragmentation and update modified statistics on all user databases

EXECUTE dbo.IndexOptimize @Databases = 'USER_DATABASES',
@FragmentationLow = NULL,
@FragmentationMedium = 'INDEX_REORGANIZE,INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE',
@FragmentationHigh = 'INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE',
@FragmentationLevel1 = 5,
@FragmentationLevel2 = 30,
@UpdateStatistics = 'ALL',
@OnlyModifiedStatistics = 'Y'

C. Update modified statistics on all user databases

EXECUTE dbo.IndexOptimize @Databases = 'USER_DATABASES',
@FragmentationLow = NULL,
@FragmentationMedium = NULL,
@FragmentationHigh = NULL,
@UpdateStatistics = 'ALL',
@OnlyModifiedStatistics = 'Y'

Execution

Execute the stored procedures from SQL Server Agent CmdExec jobs, using sqlcmd and the -b option. Pass the parameters to the stored procedures by name:
sqlcmd -E -S $(ESCAPE_SQUOTE(SRVR)) -d master -Q "EXECUTE dbo.IndexOptimize @Databases = 'USER_DATABASES'" -b
Use SQL Server Agent job output files with tokens for jobid, stepid, date, and time. Output files ensure that you always have a full set of information, in case of an error. Tokens ensure that the output files have unique file names.
You can use the MaintenanceSolution.sql script to install the SQL Server Maintenance Solution. Then the sqlcmd commands and the output files with tokens will be configured for you.

Getting Started

  1. Download MaintenanceSolution.sql.
  2. Execute MaintenanceSolution.sql. This script creates all the objects and jobs that you need.
  3. Go into [SQL Server Agent] / [Jobs] and start the jobs that have been created. Verify that these jobs are completing successfully. Check the output files in the error log directory.
  4. Schedule the jobs.

Upgrading

  1. Download MaintenanceSolution.sql.
  2. Change this line in the script so as not to create jobs:
    SET @CreateJobs = 'N'
  3. Execute MaintenanceSolution.sql. The script drops the old versions of the stored procedures and functions and creates new versions.
  4. Start the jobs and verify that they are completing successfully.

Wednesday, March 28, 2012

PowerPivot for SharePoint DataSource Issues

Over the past several weeks we have been setting up new dev enviornments for Sql Server 2012 upgrades. In doing this, we have had to upgrade the PowerPivot bits on the SharePoint/Reporting Server app servers. This has caused the PowerPivot reports to break or kick an error saying "Can't connect to datasource".  After a good bid of research we found a couple primary causes for this issue.

  • Service Account for PowerPivot permissions on the Analysis instance
    • Pull up SSMS and servername\powerpivot instance
    • Take a look at the properties of the instance
    • Make sure your service account has admin permissions
      • This is needed to be able to create new "sandbox" dynamic cubes
  • Maximum Workbook Size/Increase Excel Services Limits
    • Apparently, after upgrading these config edits are default back to a single connection and 1 MB file size. Most any PP report will result in an error as a result of this default
    • Go to Central Admin/ Application Management/ Manage Service Applications
    • Excel Service Application/Workbook Properties
      • Maximum Workbook Size update to 2000 mb
      • Maximum Char or Image Size update to 100 mb

I found a great article that helps you walk through confuigruation steps. I found this specific issue to be a major problem when trying to upgrade.


Reference Link:
http://powerpivotgeek.com/docs/PowerPivot_Existing_Farm_Installation.pdf

Thursday, March 22, 2012

Twelve Days of SQL 2012 Webinar Series

Register Today Link

Go Further. Forward. Faster. With Microsoft SQL Server 2012!


As the foundation of the cloud-ready information platform, SQL Server 2012 will help organizations unlock breakthrough insights across the organization, as well quickly build solutions and extend data across on-premises and public cloud backed by mission critical confidence.

Each session of this webinar series will highlight the new features of SQL Server 2012, including:

MISSION CRITICAL CONFIDENCE: Enable mission critical availability and performance environments at low TCO.

• The 9s you need with AlwaysOn

• Blazing-fast query performance with ColumnStore Index

BREAKTHROUGH INSIGHT: Unlock new insights with pervasive data discovery across the organization.

• Rapid data discovery via Power View and PowerPivot

• Credible, consistent data via BI Semantic Model and Data Quality Services

CLOUD ON YOUR TERMS: Create and scale business solutions fast, on your terms from server to private or public cloud.

• Scale on demand from devices to datacenter to cloud

• Write applications once, run most anywhere with SQL Server Data Tools

Wednesday, January 4, 2012

SSAS 2008 R2 Config File Edits

If you need to change the location of the AS data directories the .ini file will allow you to control each of the files needed for the instance.


From Config File:

Get the location of Config File of Current Instance.


Open Services.msc, look for Analysis Services Instance, in Path to executable look for the path of Config Directory it will appear something like this:

("C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Config")

Stop Analysis Services from Configuration Manager or from SQL Management Studio

Open Config Directory take a backup of existing file – msmdsrv.ini

Using Notepad open Config file (msmdsrv.ini ) and make changes with below mentioned Parameter.

Current Location: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data to New Location D:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data

Copy Data Directory to New Location (Recommendation Don’t Move (Cut and Paste) instead Copy and Paste)

Start Analysis Services

Open Management Studio

Check All Databases are Present

Tuesday, January 3, 2012

SSAS Articles

http://ssas-wiki.com/w/Articles#Performance

Wednesday, October 5, 2011

SSRS Embedded VB Script

In my case I am needing a UserName function to bind to the parameters. The goal is to limit the location parameters based on the UserName. So I added a UserName vb function in the embedded code section of the report. 

Go to Report > Properties > Code

Add the following function:
Public Function UserName()
     Try
          Return Report.User!UserID
     Catch
          Return "System"
      End Try
End Function

Now go to Parameters and set default value of UserName to: =code.UserName()

This will bind your userName function to the actual UserName parameter.

Good luck

Friday, July 29, 2011

Fix Slow WebDAV Performance in Windows 7

Today, finally, I got so sick and tired of the Slow WebDav Performance so I searched for a solution. I found the answer in just a minute or two, illustrating quite succinctly just how much time I had been wasting just “putting up with it.” Oddly, the culprit is none other than Internet Explorer 8. Quite simply, all you have to do is turn off IE’s automatic proxy settings detection. Here’s how to do that:
  1. In Internet Explorer, open the Tools menu, then click Internet Options.
  2. Select the Connections tab.
  3. Click the LAN Settings button.
  4. Uncheck the “Automatically detect settings” box.
  5. Click OK until you’re out of dialog hell.
I found the answer on this Microsoft Technet discussion, incidentally. The solution was posted by “Daniel CD” about two-thirds of the way down the page.


Reference