- Home
- Blog
- EDGEBIC How-To
- How to Connect EDGEBIC to SQL Server
To connect EDGEBIC to SQL Server, open Settings and then the DataSource tab, choose SQL Server as the provider, enter the Server and Database, pick Windows or SQL authentication, click Test connection, and then Apply and restart. EDGEBIC by User Solutions uses one shared SQL Server database so several planners see the same live plan; the connection is a few fields and a restart, and the database itself does not need to exist beforehand because EDGEBIC builds its schema on the first launch.
This post covers the connection fields and the test. For the broader choice between a local file and a shared server, see EDGEBIC deployment options explained; the full task library is at the EDGEBIC how-to hub.
Before You Start
- You have the SQL Server instance name from your IT team.
- You have either Windows-authentication rights on that server, or a SQL login and password that can create or use the database.
- You are ready to restart the application. Switching the connection always requires a restart, so save any in-progress edits first.
The Steps
- Open the DataSource tab. From the main navigation open Settings, then the DataSource sub-tab. The card at the top shows the active connection with a green Connected chip.
- Select the provider. Under Database provider, choose SQL Server. (PostgreSQL and MySQL appear in the list but are not available; only SQLite and SQL Server are supported.)
- Enter the server. In Server, type the instance name or host, for example
SQLSRV01. - Enter the database. In Database, type the database name, for example
EDGEBIC_Production. It does not have to exist yet. Use Refresh to list databases already on the server if you are joining an existing one. - Choose authentication. Under Authentication, pick Windows (recommended, no password) or SQL Server (a named login). For SQL Server, fill in User and Password; the password is stored encrypted and tied to your Windows account.
- Test the connection. Click Test connection. Read the status line below the button. It tells you plainly whether the server is unreachable, sign-in failed, or the server is reachable and the database will be created on first launch.
- Apply and restart. On the warning card, click Apply and restart. If you want a safety copy of the current database first, click Export current first. EDGEBIC restarts on the new connection.
What Changes When You Save
| Surface | Effect |
|---|---|
| The application | Closes and restarts immediately on the new connection. |
| The SQL Server database | Created automatically with a full schema if it did not exist. |
| The old database | Untouched. You can switch back from the same screen at any time. |
| Users and sign-in | Users live inside the database, so a brand-new database asks you to create an administrator again. |
| SQL passwords | Encrypted against your Windows account; another account or machine must re-enter them. |
How to Check It Worked
After the restart, open Settings and then DataSource again. The connection card at the top should show a green Connected chip, the SQL Server provider, and the server and database you entered. If a brand-new database was created, you will also have just gone through the administrator creation and the setup wizard again, which is confirmation the new database is live.
Common Mistakes
Reading "database does not exist" as a failure. It is the expected result for a new database. The server is reachable, your sign-in worked, and EDGEBIC creates the database on the next launch.
Assuming the connection copies your data. Connecting to a new SQL Server database gives you an empty database. Moving data across is a separate step, covered in how to switch from SQLite to SQL Server in EDGEBIC.
Choosing SQL authentication by habit. The saved SQL password is bound to one Windows account. On a multi-user team that means each person re-enters it. Windows authentication avoids the whole problem.
Forgetting the login needs rights. If the database does not exist, your login must be allowed to create it, or IT must pre-create the database and grant your account access. A reachable server with no create rights fails at first launch, not at Test connection.
What to Do Next
With the connection made, the next moves are migrating data and setting up people. How to switch from SQLite to SQL Server in EDGEBIC walks the full changeover including what does not carry over, and moving EDGEBIC from one planner to a shared server covers the habits a shared plan needs. To point the current provider at a different database or restored file, see how to change the database connection in EDGEBIC. The EDGEBIC product page shows where the shared database sits in the platform.
Expert Q&A: Deep Dive
Q: Test connection says the database does not exist. Did I get the name wrong?
A: Probably not. That message is the normal, healthy result when the server is reachable and your sign-in succeeded but the database you named has not been created yet. EDGEBIC creates it for you on the first launch after Apply and restart, so you can proceed. The test deliberately distinguishes three cases so you always know where you stand: server unreachable, sign-in failed, and server reachable with the database still to be created. Only the first two are problems. If you did mean to connect to an existing database, use Refresh next to the Database field to list the databases already on the server and pick the right name.
Q: I entered a SQL login and it worked on my machine, but a colleague copied my settings and cannot sign in. Why?
A: The SQL authentication password is stored encrypted and tied to the Windows account that entered it, so it cannot be decrypted under a different Windows account or on a different machine. Your colleague does not need your file at all: on their own machine they open Settings and then DataSource, select SQL Server, enter the same server and database, re-enter the SQL password under their own Windows account, and click Apply and restart. The cleaner fix for a team is Windows authentication, which stores no password and sidesteps the issue entirely.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.
