Using the Where to Put the SnapInfo Directory for Each Database screen

In the unlabeled list, select the individual database that you want to map to a dedicated SnapInfo directory.

In the Disk List, select the LUN on which you want to create the SnapInfo directory for the database.

Click the move (<=>) button.

Result

The Database SnapInfo Directory Path List displays the location at which the SnapInfo directory will be created. The SnapInfo directory for the selected database will be stored at this location rather than at the default location for the SQL Server instance.

Note
The Configuration Wizard will allow you to create the SnapInfo directory only in valid locations. For more information, see SQL Server database configuration restrictions enforced.

If you want to unmap the SnapInfo directory for an SQL Server database, do the following.

1. In the Database SnapInfo Directory Path List, select the SQL Server database.
2. Click Reconfigure.

Result

The mapping is removed from the Database SnapInfo Directory Path List. The SQL Server instance is returned to the list of unconfigured SQL Server databases, and you can reassociate its SnapInfo directory with any available LUN.

By default, the SnapInfo directory name is SMSQL_SnapInfo. If you want to specify a different location or name, complete the following steps.

1. In the Database SnapInfo Directory Path List, select the database for which you want to change the location or name of the SnapInfo directory.
2. Click Details.

   The Default SnapInfo Property dialog box appears and displays the current location specified for the SnapInfo directory for the selected database.

3. In the New SnapInfo Directory Path box, enter the new path.
4. Click OK.

   The dialog box closes, and the To column of the Database SnapInfo Directory Path List displays the new location for the SnapInfo directory for the selected database.

   Note
   The Configuration Wizard will allow you to create the SnapInfo directory only in valid locations. For more information, see SQL Server database configuration restrictions enforced.