Skip to content
  • There are no suggestions because the search field is empty.

Restart SQL Services

This article helps Webgility Desktop users understand when and how to restart SQL Server services to ensure Webgility Desktop functions properly. Restarting SQL services may be required after configuration changes, software updates, performance issues, maintenance activities, or potential security concerns. The article provides step-by-step instructions for restarting SQL Server and SQL Server Browser services in Windows, followed by reopening Webgility Desktop to complete the process.

Overview:

SQL Server services may need to be restarted for various reasons, including:

  1. Configuration changes: When you make changes to the SQL Server configuration settings, such as changing memory allocation, network settings, or security configurations, you may need to restart the SQL Server services for the changes to take effect.

  2. Software updates: When you install software updates for SQL Server, such as service packs, cumulative updates, or hotfixes, you may need to restart the SQL Server services to complete the installation.

  3. Performance issues: If the SQL Server services are not responding or are experiencing performance issues, restarting the services may help to resolve the problem.

  4. Maintenance activities: You may need to restart the SQL Server services as part of regular maintenance activities, such as backups, restores, or database maintenance.

  5. Security issues: If you suspect that the SQL Server services may have been compromised or that there is a security breach, restarting the services may help to mitigate the risk.

Steps to restart services

  • Type services in the Windows search bar and click ‘Open’
  • Look for the SQL Server [Instance name for Webgility], Right-click on ‘SQL Server [Instance name for Webgility]’, and click Restart. Similarly, right-click on the services for ‘SQL Server Browser’ and restart the services as mentioned above.
  • Once done re-open Webgility Desktop.