Tag Archives: data security

Instant Inventory Information

Do you ever wonder where that stack of widgets is? How long did that vendor say it would take to get us those fizzbinns? Is Project Z-180 ever going to be completed? These very important questions always occur when handling your inventory concerns.

With SIMMS Inventory Management software, you can always get these answers quickly and easily. Analytical reports and project management features enable SIMMS users to keep complete control of more than just inventory – it also allows scheduling of projects and can provide data needed for getting ongoing projects finished and out the door.

Contact KCSI today to learn more about getting quick answers to your most important questions.

Data Integrity with SIMMS

The SIMMS Inventory Management system enables users to keep confident of their data and system.

Firstly, backups of SIMMS Installer files should be made each time a service pack or full version is released. This always guarantees you have the tools available to re-establish your installation in case any update to your operating system or its features.

Secondly, your company files (databases) can be backed up as often as one’s in-house IT Department schedules them. If each week sees dozens of transactions occurring then weekly backups are advised and can be performed manually by any administrative user. If your established backup protocol is either more often or less often than weekly, then you can conduct the backup process any time.

Regular backups guarantee the integrity of your data at all times and make for easy restoration at whatever time you want or need to perform one.

Contact KCSI today to learn the simple steps to accomplish true security of your SIMMS system.

SIMMS Database Backups

To back up a SIMMS SQL Database:

  1. After connecting to the appropriate instance of the Microsoft SQL Server Database Engine, in Object Explorer, click the server name to expand the server tree.
  2. Expand Databases, and depending on the database, either select a user database or expand System Databases and select a system database.
  3. Right-click the database, point to Tasks, and then click Back Up. The Back Up Database dialog box appears.
  4. In the Database list box, verify the database name. You can optionally select a different database from the list.
  5. You can perform a database backup for any recovery model (FULL,BULK_LOGGED, or SIMPLE).
  6. In the Backup type list box, select Full.

    Note that after creating a full database backup, you can create a differential database backup; for more information, see Create a Differential Database Backup (SQL Server).

  7. Optionally, you can select Copy Only Backup to create a copy-only backup. A copy-only backup is a SQL Server backup that is independent of the sequence of conventional SQL Server backups. For more information, see Copy-Only Backups (SQL Server).
  8. For Backup component, click Database.
  9. Either accept the default backup set name suggested in the Name text box, or enter a different name for the backup set.
  10. Optionally, in the Description text box, enter a description of the backup set.
  11. Specify when the backup set will expire and can be overwritten without explicitly skipping verification of the expiration data:
    • To have the backup set expire after a specific number of days, click After (the default option), and enter the number of days after set creation that the set will expire. This value can be from 0 to 99999 days; a value of 0 days means that the backup set will never expire.

      The default value is set in the Default backup media retention (in days) option of the Server Properties dialog box (Database Settings Page). To access this, right-click the server name in Object Explorer and select properties; then select the Database Settings page.

    • To have the backup set expire on a specific date, click On, and enter the date on which the set will expire.

      For more information about backup expiration dates, see BACKUP (Transact-SQL).

  12. Choose the type of backup destination by clicking Disk or Tape. To select the paths of up to 64 disk or tape drives containing a single media set, click Add. The selected paths are displayed in the Backup to list box.

    To remove a backup destination, select it and click Remove. To view the contents of a backup destination, select it and click Contents.

  13. To view or select the advanced options, click Options in the Select a page pane.
  14. Select an Overwrite Media option, by clicking one of the following:
    • Back up to the existing media set

      For this option, click either Append to the existing backup set or Overwrite all existing backup sets. For more information, see Media Sets, Media Families, and Backup Sets (SQL Server).

      Optionally, select Check media set name and backup set expiration to cause the backup operation to verify the date and time at which the media set and backup set expire.

      Optionally, enter a name in the Media set name text box. If no name is specified, a media set with a blank name is created. If you specify a media set name, the media (tape or disk) is checked to see whether the actual name matches the name you enter here.

    • Back up to a new media set, and erase all existing backup sets

      For this option, enter a name in the New media set name text box, and, optionally, describe the media set in the New media set description text box.

  15. In the Reliability section, optionally check:
  16. If you are backing up to a tape drive (as specified in the Destination section of the General page), the Unload the tape after backup option is active. Clicking this option activates the Rewind the tape before unloading option
  17. SQL Server 2008 Enterprise and later supports backup compression. By default, whether a backup is compressed depends on the value of the backup-compression default server configuration option. However, regardless of the current server-level default, you can compress a backup by checking Compress backup, and you can prevent compression by checking Do not compress backup.

Security Blankets

The SIMMS Inventory Management system enables users to keep confident of their data and system. Firstly, backups of SIMMS Installer files should be made each time a service pack or full version is released. Secondly, company files (databases) can be backed up as often as one’s in-house IT Department schedules them. If each week sees dozens of transactions occurring then weekly backups are advised and can be performed manually by any administrative user. Contact KCSI today to learn the simple step to accomplish true security of your SIMMS system.