This article describes recommended maintenance activities for Snow Commander databases hosted on Microsoft SQL Server, including configuration steps and scheduled tasks to maintain optimal database performance. The instructions help ensure proper growth management, integrity checks, and prevent long-term performance degradation.
Important: All of the queries and examples in this article are prepared for a database named commander.
General configuration
- Do not restrict database growth; restricting maximum size can prevent normal Commander operations such as synchronizing VM states.
- The default recommendation is to disable auto-shrink by running:
ALTER DATABASE commander SET AUTO_SHRINK OFF;
Autogrowth settings
To confirm and configure autogrowth for the Commander database:
- Connect to the database server using SQL Management Studio.
- Expand Databases, right-click the commander database, and select Properties.
- Go to the Files page and locate the Autogrowth / Maxsize column.
- Click each line (database file and log file) to set:
- Database file (commander.mdf):
- Enable Autogrowth
- File Growth: In Megabytes → 1MB
- Maximum File Size: Unlimited
- Log file (commander_log.ldf):
- Enable Autogrowth
- File Growth: In Percent → 10%
- Maximum File Size: Unlimited
- Database file (commander.mdf):
- Click OK twice to save.
Alternatively, run the following queries:ALTER DATABASE [commander] MODIFY FILE ( NAME = 'commander', MAXSIZE = UNLIMITED, FILEGROWTH = 1MB ); ALTER DATABASE [commander] MODIFY FILE ( NAME = 'commander_log', MAXSIZE = UNLIMITED, FILEGROWTH = 10% );
Transaction log management
Flexera recommends the simple recovery model for most environments to reduce log file size. Use full recovery only if auditing without data loss is mandatory.
To configure recovery model:
- In Object Explorer, right-click the Commander database and select Properties.
- Switch to the Options page and set Recovery Model to Simple or Full based on your requirements.
- Click OK.
Create the defragmentation task
To reduce fragmentation and improve performance:
- Download and run the queries included in the attached zip file against the Commander database in this order:
- CommandLog.sql
- CommandExecute.sql
- IndexOptimize.sql
- In Object Explorer, expand SQL Server Agent.
- Right-click Jobs and select New Job…
- On the General page, name the job Defrag Commander DB and set the Owner (typically commander connection user or sa).
- Switch to the Steps page and click New…
- Enter Step Name as Execute Command.
- Set Type to Operating system (CmdExec) and Run as to SQL Server Agent Service Account.
- Enter the following command (replace
commanderwith your database name):sqlcmd -E -S $(ESCAPE_SQUOTE(SRVR)) -d commander -Q "EXECUTE [dbo].[IndexOptimize] @Databases = 'commander', @LogToTable = 'Y', @TimeLimit = '3600', @UpdateStatistics = 'ALL'" –b - Configure notifications as needed (for example, write to Windows Application event log on failure).
- Click OK twice to save.
Create the maintenance plan
Set up a plan to schedule recommended tasks during low-activity periods:
- In Object Explorer, expand Management. Right-click Maintenance Plans and select New Maintenance Plan.
- Provide a name and click OK.
- Drag tasks from the Toolbox to the plan and link them in sequence using green arrows. Recommended tasks:
- Index defragmentation and statistics updates
- Corruption detection
- Backup
- History and maintenance cleanup
- Open each task to configure options as described in their respective sections.
- Click Schedule to set up a weekly run (Saturday or Sunday night is typical).
- Save and close the plan.
To run corruption detection manually:DBCC CHECKDB ('commander') WITH NO_INFOMSGS, ALL_ERRORMSGS;
Backup recommendations
Perform nightly full database backups. Manual backups are also required before upgrades or major changes. Verify if third-party backup processes exist to avoid conflicts.
History and maintenance cleanup
Add a History Cleanup Task to remove records older than four weeks for:
- Backup and restore history
- SQL Server Agent job history
- Maintenance plan history
Specify the folder storing backups and backup file extension (typically .bak).
Outcome
These steps ensure your Commander database runs efficiently, scales appropriately, and remains resilient against corruption while maintaining clean maintenance histories.
Related Articles
Plan AWS RDS maintenance for Snow Commander 11Number of Views Creating a SQL Database backup of Snow Inventory and Snow License Manager to send to Snow Support 39Number of Views Snow Commander Portal Language - Upgrade SQL Database Collation 9Number of Views Configuring Azure AD for SSO with Snow Commander 34Number of Views Microsoft SQL server editions can't be determined correctly from SCCM 18Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago