How to: Resolve StabiBASE and Stabicad slowness by restarting SQL Server service after updates
div dir="auto">
Understanding the Issue
Most Stabicad environments utilize Microsoft SQL Server Express. SQL Server Express is hard-limited by Microsoft to use a maximum of 1 GB to 1.4 GB of RAM per database instance. During routine operations—and particularly after Windows or SQL Server updates—the server fills this memory buffer with query execution plans and cached data.
Once this 1.4 GB memory ceiling is reached, SQL Server cannot allocate RAM for new database queries requested by Stabicad or StabiBASE. This results in:
- StabiBASE hanging or taking several minutes to open.
- Delayed responses when inserting symbols or modifying element properties.
- Database connection timeout error messages.
Step-by-Step Resolution: Restarting the SQL Service
To flush the saturated query cache and free up the SQL RAM memory buffer, restart the SQL Server service on the database server:
- Log in to the server hosting the Stabicad SQL database (or open Task Manager on the server workstation).
- Press Windows Key + R, type
services.msc, and press Enter. - In the Services list, locate your Stabicad SQL Server instance, typically named:
SQL Server (STABICAD)SQL Server (SQLEXPRESS)
- Right-click the service name and select Restart.
- Wait a few seconds until the service status returns to Running.
Outcome: The RAM buffer pool and query cache are flushed instantly. StabiBASE and Stabicad will now open and query data at normal speeds.
Preventative Recommendations for System Administrators
- Automated Weekly Maintenance: Set up a Windows Scheduled Task on the server to automatically restart the
SQL Server (STABICAD)service outside of business hours (e.g., every Sunday night). - Upgrade Considerations: If your company database size exceeds 5 GB or supports more than 15 concurrent draftsmen, consider upgrading from SQL Server Express to SQL Server Standard edition to remove the 1.4 GB RAM limit.