SQL CE
The database type "SQL Compact Edition" or "SQLCE" is a database file stored within the Factory Database folder. It has an SDF file extension, and some users call it a 'local' database, meaning that it resides locally on each computer. This is not to be confused with the SQL Local database discussed in the next section, "SQL Local (LocalDB)."
This is the default database type used when you install Microvellum.
SQL Compact Edition is limited to a single connection to the database at any one time. This means that if you have a company where multiple Users need to access the same data, you cannot use this database type and will need to set up a SQL Server type database.
SQL Local (Local DB)
Structured Query Language Local Database. SQL Local DB copies a minimal set of files necessary to start the SQL Server Database Engine. SQL Local DB is suitable for a single-user or multi-user environment. SQL Local has a 10GB limit imposed by Microsoft. SQL Local DB is part of the Microvellum process to transition from an Individual Work Order Database to a single Unified Work Order Database.
SQL Local - Factory Connection
Used to convert a Factory SQL CE Database to an SQL Local (LocalDB) Database. Click the button Transfer SqlCe to Sql Local to initiate the process.
SQL Local - Work Order Connection
Used to convert Work Order SQL CE Databases into a single SQL Local Database. This step is necessary when transitioning to a single work order SQL Server database. Specify the type of database before clicking on the button Transfer SqlCe to Sql Local.
SQL Server
The SQL Server database type supports the connection of multiple computers connected to the same data through a network. To use this database type, you must first set up a SQL Server using Microsoft SQL Studio Manager.
SQL Server - Factory Authentication
SQL Server databases require authentication information to establish a successful connection. The configuration of the SQL Server instance determines the type of Authentication necessary in this section, as well as the User Name and Password.
Windows – Uses internal Windows user data to connect to the SQL Server database. You must configure the server instance with one option or the other when you create the server instance.
SQL Server – Uses the "SQL Server User Name" and "SQL Server Password" entered in the same area of the interface.
SQL Server - Factory Connection
SQL Server instances and their databases require Data Source and Data Catalog information for a successful connection.
Data Source – Specifies the SQL Server instance name containing the desired database.
Data Catalog – Specifies the SQL Server database name to which you are connecting.
Test Factory Connection – Verifies the connection to the Factory database to ensure successful communication with the SQL Server.
Transfer SQLCE to SQL Server – Transfers an existing SQL CE Database to the SQL Server Database. Transfer will overwrite all existing SQL Server Information. Use caution with this command if you are transferring data to an existing database.
SQL Server - Work Order Authentication
The "Unified Work Order Database" SQL Server database requires authentication information for a successful connection. The configuration of the SQL Server instance determines the type of Authentication necessary in this section, as well as the User Name and Password.
Windows – Uses internal Windows user data to connect to the SQL Server database. You must configure the server instance with one option or the other when you create the server instance.
SQL Server – Uses the "SQL Server User Name" and "SQL Server Password" entered in the same area of the interface.
SQL Server - Work Order Connection
Unified Work Order Database connection settings. Data Source and Data Catalog (Work Order and Geometry) information required for a successful connection to the SQL Server and Database.
Data Source – Specifies the SQL Server Unified Work Order Database instance name containing the desired database.
Data Catalog (Work Order) – Specifies the SQL Server Unified Work Order Database name to which you are connecting.
Data Catalog (Geometry) – Specifies the SQL Server Unified Geometry Database name to which you are connecting.
Test Work Order Connection – Verifies the connection to the Unified Work Order database to ensure successful communication to the SQL Server.
Test Geometry Connection – Verifies the connection to the Unified Geometry database to ensure successful communication to the SQL Server.
Transfer SQLCE to SQL Server – Transfers an existing SQL CE Database to the SQL Server Database. Transfer will overwrite all existing SQL Server Information. Use caution with this command if you are transferring data to an existing database.
Troubleshooting Connection Failures
If you see an error such as "Cannot connect to server!" when opening or launching Microvellum, work through these checks before assuming the database itself is damaged:
Confirm the Data Source and Data Catalog values are typed exactly as configured on the SQL Server (no typos, correct instance name if using a named instance, e.g.
SERVERNAME\INSTANCENAME).Use Test Factory Connection (and Test Work Order Connection, if applicable) on this page to isolate whether the failure is in the Factory database or the Work Order database.
Try the server's IP address instead of its hostname if the Data Source uses a domain name — some networks resolve DNS differently for different applications, and switching to an IP address rules this out.
Confirm SQL Server is reachable on the network — port 1433 (TCP) must be open for the connection itself, and port 1434 (UDP, SQL Server Browser) must be open if you're connecting to a named instance rather than a default instance. See the Firewall & Network Configuration section of Microvellum BSB License Activation Troubleshooting for the full port/executable list.
Check Windows vs. SQL Server authentication — if the SQL Server instance is configured for one and this page is set to the other, the connection will fail even with correct credentials.
New workstation / new install: if this is a freshly set up computer, confirm it isn't blocked by a local firewall or antivirus rule that hasn't yet been added for this machine.



