During the course of investigating a technical support issue for Snow Software® Commander®, the need may arise to backup your Microsoft SQL database. To do so, you will use Microsoft SQL Server Management Studio. If you did not install this when you installed SQL, you can install it from the original source.
Alternatively, you can download Management Studio Express, and use it to run the queries.
Connecting to Your Database
Follow the procedure below to connect to your Snow Software Commander database.
- Login to a computer where SQL Server Management Studio is installed.
- Launch SQL Management Studio from the Start menu.
- Choose Database Engine as the Server type, choose the correct Server Name from the list or browse for the correct server.
If your user account has rights to access the database, leave Authentication as Windows Authentication. Otherwise, switch it to SQL Server Authentication and enter the User name and Password for a SQL account with rights to access the database.Note: If you are not sure which account to use, you can confirm what's being used by Snow Software Commander by opening the Commander Control Panel.
4. Click Connect.
Performing the Backup
Now that you are connected, you can proceed with performing the backup. Before you begin the next procedure, make sure that you have access to as much disk space as is required for the backup file.
- In the Object Explorer pane, expand the SQL Server housing your Snow Software Commander database.
- Right-click your Commander database and choose Tasks > Backup.
Performing a backup of the Snow Software Commander database as part of regular maintenance will also help to keep the size of the transaction log down to a manageable amount. Depending on your environmental needs, you may wish to also include a shrink, but remember when you do so your are trading the disk footprint for SQL performance speeds, as SQL must create white space to which records are written, and shrinking eliminates this white space.
Snow Software cautions against using third-party backup utilities, as testing has shown that some do not correctly trigger a SQL Server checkpoint upon successful completion. You can easily determine if this is an issue with your backup software by observing the size of the log file before and after a backup completes successfully. If the size of the log is not reduced by the backup followed by a shrink operation, you should use the built-in SQL backup engine rather than the third-party utility.
Related Articles
Restoring the Commander® Database Using SQL Management Studio 5Number of Views Backup the Commander® Database with pgAdmin 6Number of Views Creating a SQL Database backup of Snow Inventory and Snow License Manager to send to Snow Support 36Number of Views Sanitizing the Commander® Database 6Number of Views Running Queries Using SQL Server Management Studio 7Number 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. | |
Case id: 00001065
Activity: Status change: 2 hours ago