When it comes to resolving table fragmentation, the basic checkout you perform is to run DBCC INDEXDEFRAG or even run DBCC DBREINDEX statements. As per the default configuraiton SQL Database Engine allocates a new extent to an allocation unit only when it cannot quickly find a page in an existing extent with sufficient space to hold the row being ...

All of sudden the re-org of an index started failing and no error was displayed within that scheduled job we execute. After executing the code from Query Editior I was able to get the message as follows: Msg 2552, Level 16, State 1, Line 3 The index ''<name>'' (partition 1) on table ''TableName'' cannot be reorganized because page level ...

Within your SQL Server environment there are few simple steps you can take up in order to gain performance to a level, for instance when configuring a SQL Server that will only contain a few gigabytes (GB) of data and not sustain heavy read nor write activity, it is not as important to be concerned with the subject of disk I/O and balancing of SQL ...

You may be aware that the indexes on a SQL Server database take up space, so in case of unused indexes its obvious that they waste storage. It is easy to find the indexes using SP_HELPINDEX statement against a table, so to identify the unused indexes what is the way out. In the previous versions of SQL Server Index Tuning wizard is only way out, ...

I believe since Windows 2000 server days you can take advantage of Indexing Service that creates indexes of the contents and properties of all files on local and network drives in order to increase file searching speed. It's quite similar to ''Find Fast'' that ships with Microsoft Office. There is a downside in using this option on a Windows ...