SQL Server uses data files which are resized automatically as the data grows, until the disk is full. When this happens, you can add another data file on a different disk. The following tasks are used frequently when you need to perform database maintenance tasks on SQL Server.
Add a filegroup — Filegroups are used as containers for datafiles. A filegroup can be connected to one database only. Usually, two filegroups are used for each domain: one for data tables and the other for table indexes. You can backup and restore data for a filegroup. A primary filegroup contains stored procedures and triggers. When deleting a domain, the entire filegroup and the datafiles it contains are deleted, resulting in cleaner data, without causing damage to the database.
Print filegroup information — This procedure explains how the System Administrator can display the list of all the existing SQL Server filegroups and print out the filegroup information.
Add a log file — The database log file is used internally by SQL Server to backtrack aborted user sessions. This way you can resume any previous sessions that you stopped or canceled. This procedure explains how to add a log file.
Add a datafile to the TEMPDB database — This procedure enables you to add a datafile to the SQL Server TEMPDB Database. This database is used internally by the SQL Server to make all the required temporary operations. Such operations are needed when Smart Instrumentation brings data in a certain order, and the database needs to sort this set of data after retrieving it.
Optimize indexes — This procedure enables you to optimize fragmented SQL Server indexes. The SQL Server indexes become fragmented during the domain lifetime and contributes to database under-performance. In this case you can rearrange your SQL Server indexes to optimize them. As you keep storing and deleting domain data, the SQL Extents become disordered thus slowing down SQL command execution. Smart Instrumentation solves this problem by reordering the indexes stored in these Extents.