Help

How to: Update or migrate an outdated SQL Server to a newer version on a server

Modified: 9 Jun 2026 Stabicad
Not version-specific
Stabicad
Context: Why update the SQL Server?
From time to time, support for outdated SQL Server versions expires. Through its built-in tools, Stabicad always provides a current, supported version (such as SQL Server 2019). During an update, the software may detect that your current database is running on an outdated SQL version. The database must then be transferred to the newer instance. Note: This solution is strictly intended for updating a SQL Server in a Server environment! Local SQL Server instances are automatically updated by StabicadSetup.
 
Phase A: Installing the new SQL Server (if not already present) Do you already have a current SQL Server (e.g. 2017 or newer) running? Then proceed directly to Phase B.
  1. Place the Stabicad installation files on the server and start the Setup.
  2. Choose the language and accept the license terms.
  3. In the wizard, select Tools  and then select MS SQL Server.

 

  1. Click Install. The installation data is now collected and the new SQL version is installed. (Note: Do you get the message "Installation failed"? Then this SQL version is probably already installed on your server).
  2. Important: Exclude the sqlservr.exe process of the new SQL Server in your Windows Firewall. You can find this file in the corresponding installation folder, for example: C:\Program Files\Microsoft SQL Server\MSSQLxx.MSSQLxxxx\MSSQL\Binn.
Phase B: Migrating the database via Network Installation After the new SQL environment is running on the server, the data still needs to be transferred.
  1. Place the Stabicad installation files on a local workstation and start the Setup.
  2. Choose the language, accept the terms and choose Network Installation.
  3. Under Installation Configuration, the path where your current StabiBASE is installed is filled in (this is greyed out). Click Next.
  4. The Database Server screen reads your current connection data. Click Next.
  5. The Database Server Migration screen appears. This shows the new server instance you created in Phase A. Check if the correct Database name is entered, so the current database is transferred properly. Click Next.  
  6. Click Install in the overview screen. A backup of the old database is now made fully automatically, which is then restored into the new SQL environment on the server.
Phase C: Checking Service permissions (Log on as) Finally, you must check whether the service of the new SQL Server has the correct permissions.
  1. Open the Windows Start menu on the server, type Services.msc and press Enter.
  2. Search the list for the new SQL server service (e.g. SQL Server (STABICAD2019) or similar).
  3. Check the Log on as (Aanmelden als) column. This must be set to Local System.
  4. Is it set differently? Right-click it, choose Properties, go to the Log On tab, select Local System account and save.  

 

Submit