Server Sandbox Configuration

Server Sandbox Configuration

This document explains the steps to configure a server sandbox. For additional information about what a "sandbox" is and its uses, click here.

Before creating a sandbox environment, we strongly recommend the user back up their production data.

Set Up Toolbox

  1. Open Toolbox in an SQL configuration.
  2. Create a "Sandbox Server" data folder:
    1. Select the "Help" tab from the primary Toolbox palette and select "Browse to Factory Data."
    2. Copy the "Clipboard," "Drawing Templates," and "Graphics" folders as well as the Toolbox Template file.

    3. Go up a folder level by selecting the "Up" arrow -> On this level, create a new folder named "Sandbox Server" -> Paste the items copied above into this folder.
    4. Within the "Sandbox Server" folder, create two new folders named: "Factory Database" and "Work Orders."
    5. Populate the "Factory Database" folder by copying five of your most recent project folders, or particular projects you wish to test, from the original "Factory Database" folder. Do the same for the "Work Orders" folder. 
    6. The entire "Microvellum Data" folder could be copied and renamed to: "Sandbox Server." We recommend only choosing an assortment of your most recent projects and work orders strictly for speed purposes. Depending on the number of projects and work orders you have, the process of copying the entire "Microvellum Data" folder could take a long time.  
  3. Restart Toolbox.
  4. Select "Manage Configurations."
  5. Copy the SQL server configuration and rename it "Sandbox Server."
  6. Start Toolbox in the "Sandbox Server" configuration created in the last step.

Creating a Sandbox Server

Creating a new sandbox server consists of two processes. Creating a backup of the source database, and creating a new database from the backup.

Create a Backup

  1. Open SQL Server Management Studio.
  2. Right-click the existing Data Catalog and select “Tasks” > “Back Up...”  
  3. The existing Data Catalog is found in the "Data Access" tab of the Options menu in Toolbox. 

  4. Make sure that the Backup Type is set to "Full."
  5. Check the Destination field to verify the path where the backup will be saved.
  6. If this field is blank or incorrect, click the Add button. You can remove the entry in the field by clicking the Remove button. You may want to do this if you do not want to overwrite a previous backup file.
  7. If you select the Add button, you will be prompted to select a backup destination.

  8. Use the Browse   button to select a new path for the backup file including the filename.

  9. Select the path and enter the filename that you want the backup to create including the file extension. (The standard backup convention is “filename”.BAK) Make a note of this path and filename as you will need to know them later.
  10. Click "OK" twice to get back to the main Backup Database window.
  11. Click "OK" to start the Backup.
  12. You will see a message confirming the backup is complete. Click OK.

Create New Database From Backup

  1. Right-click the "Databases" folder at the top of the "Object Explorer" pane and select "Restore Files and Filegroups...."

  2. In the "To database" field, enter a name for your new database (e.g. "Sandbox Server"). 

  3. For the source, select "From device" and click the browse   button.
  4. Click the "Add" button, then browse to the backup file you just created. Click "OK" twice.
  5. Ensure the "Restore" checkbox is selected for the source database.
  6. Select "Options" from the "Select a page" pane on the left side of the interface.

  7. Check the "Overwrite the Existing Database (WITH REPLACE)" and "Leave the database readyfor use by rolling back ... (RESTORE WITH RECOVERY)" options.
  8. Click "OK" to finalize.
  9. Navigate to folder "Security" > "Logins."
  10. For user who needs access to Sandbox Server, right-click user > "Properties" > "User Mapping" > Select "Sandbox Server" and add role membership "db_owner" > select "OK."

  11. For Unified Work Order Users: Repeat the steps above for both the Work Order database and the Geometry database, naming the new databases to be restored to "WO Sandbox" and "GEO Sandbox" respectfully. Alternatively, two new empty databases could be created for the Work Order Connection, and the data transferred to them in the "Data Access" tab of the Options menu in Toolbox.

Connect Sandbox Server to Toolbox

  1. Return to Toolbox > Navigate to the "Data Access" page of the Options menu > Point your "Data Catalog" to "Sandbox Server." If you are on Unified, point to "WO Sandbox" and "GEO Sandbox." If need be, select "Transfer SqlCe to SqlServer" for your "Work Order Connection." DO NOT transfer for your "Factory Connection."

  2. Select "Toolbox Setup" > "Options" > "Utilities" > "Change Path to Microvellum Data..." > Select the "Sandbox Server" folder created previously. 
  3. Restart Toolbox, ensuring all of the changed settings held.

The Server Sandbox Configuration is now complete and ready for testing.


    • Related Articles

    • Sandbox Environment Guide

      What is a Sandbox Environment? A sandbox environment is used for risk-free testing. It uses data that is not associated with a user’s production data. “Production” data is the data commonly used for everyday business means, and it is essential to ...
    • Creating a Local Sandbox from an SQL Server Configuration Guide

      This document explains the steps required to configure a local sandbox from an SQL server. For additional information about what a “sandbox” is and when to use one click here. Prior to creating a sandbox environment, we strongly recommend the user ...
    • How to Setup a Local Sandbox Environment

      This document explains the steps to configure a local sandbox. For additional information about what a “sandbox” is and when to use one click here. Before creating a sandbox environment, we strongly recommend the user back up their production data.  ...
    • Sandbox Testing, Training & Production Environments

      The purpose of this document is to explain the Microvellum recommendation for sandbox testing, training, and production environments. To configure a sandbox environment, click here . Microvellum strongly recommends a workstation dedicated to sandbox ...
    • Introduction to the Microvellum Configuration Manager

      The Configuration Manager (available in build 15.6 and above) makes it easier and less error-prone to share configurations around your organization. For example, perhaps you want to pass the data and settings from one computer using an older version ...
    • Recent Articles

    • Toolbox Release Notes | Build 24.1.0416.641

      The following release notes apply to Toolbox build 24.1.0416.641. Maestro Toolfile Fix There was an issue with Maestro SCM Toolfiles reportedly experienced by some users, wherein the labels output by autolabeling would be in incorrect positions, an ...
    • Toolbox Release Notes | Build 24.1.0409.641

      The following release notes apply to Toolbox build 24.1.0409.641 Saw Delimited Processing Station Figure 1: The Saw Delimited option in a custom processing station. New options have been added to saw processing stations to allow for control over data ...
    • Toolbox Release Notes | Build 24.1.0328.641

      The following release notes apply to Toolbox Build 24.1.0328.641 Fillet Token Fixes Issues were discovered in the use of fillet tokens on products that also had the IRIB setting enabled: Some users processed work orders with rounded parts, which ...
    • Microvellum Foundation Library Release Notes | Build 24.0322

      Additions Added the Master Angled Ends Cabinet. Added a Global prompt, "Hinge Plate Offset From Front" for easier control. Added “Double Division” option to Horizontal Designer Cabinets, 3 Door Cabinets, and other similar products. Added a new ...
    • Common Floating License Connectivity Issues

      This document lists common issues reported by users regarding the topic of Microvellum’s Floating License Activation (FLA) and the connectivity required for FLA to function. Firewall Blocking Activation of Floating License Some users have had an ...