During the course of investigating a technical support issue for Embotics® vCommander®, 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 Embotics vCommander database.

  1. Login to a computer where SQL Server Management Studio is installed.
  2. Launch SQL Management Studio from the Start menu.
  3. 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 Embotics vCommander by opening the vCommander 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.

  1. In the Object Explorer pane, expand the SQL Server housing your Embotics vCommander database.
  2. Right-click your vCommander database and choose Tasks > Backup.

  3. When backing up a database to provide to Embotics technical support, the default options are sufficient.  Note the location where the backup file will be created, listed under the Destination section, and click OK.


Performing a backup of the Embotics vCommander 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.

Embotics 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.


See Also