Connection settings
Navigate to the Settings page in shopMaster to configure your database connection.Enter server details
Provide your SQL Server connection information:
The name or IP address of your SQL Server instance (e.g.,
localhost\SQLEXPRESS or 192.168.1.100)The name of the database containing your product table
The name of your product table to sync (e.g.,
Products, Inventory)Choose authentication method
Select your preferred authentication method from the Security dropdown:
Windows Authentication
Uses your Windows credentials to connect to SQL Server. This is the default and recommended method for local installations.Windows Authentication requires that your Windows user account has access to the SQL Server database.
Password Authentication
Uses SQL Server login credentials. When you select Password from the Security dropdown, additional fields appear:Your SQL Server login username
Your SQL Server login password (displayed as asterisks)
Test your connection
Click Test Connection to verify your database settings. shopMaster will:
- Attempt to connect to your SQL Server database
- Validate your Digible account credentials
- Display a status message for both connections
The test connection checks both your local database and Digible account to ensure end-to-end connectivity.
Complete configuration
Once the connection test succeeds, click Configure to:
- Save your settings to a
.envfile - Create the
ChangeLogtable in your database - Set up database triggers for INSERT, UPDATE, and DELETE operations
Database requirements
Your product table must include these columns:ProductID(VARCHAR(25)) - Primary keyProductName(VARCHAR(75)) - Product nameSellPrice(NUMERIC(18, 2)) - Product priceQrCode(VARCHAR(100)) - Optional QR codeStatus(INT) - Product status
ChangeLog table and three triggers (trgAfterInsert, trgAfterUpdate, trgAfterDelete) to track changes. See the change tracking guide for details.
Stored credentials
Your database credentials are saved to a.env file in the shopMaster installation directory:
Keep your
.env file secure. It contains sensitive connection information.Troubleshooting
If the connection test fails:- Verify SQL Server is running and accessible
- Check that the database and table names are correct
- Ensure your user account has read/write permissions
- Confirm ODBC Driver 17 is installed
- For Windows Authentication, verify your Windows user has SQL Server access
- For Password Authentication, check that SQL Server authentication is enabled