How to remove Ghost SQL Instances
These methods are to be verified by local IT and risks accepted by local IT. These are common procedures to remove ghost instances from SQL server and has nothing to do with DentalWriter or NPM software.
Targeted Command Line Removal
Run this command from an elevated (Administrator) Command Prompt. It targets the instance ID and only the Database engine feature (SQL), leaving shared tools alone.
1. Open Command Prompt as Administrator.
2. Execute this command: change directory to the installation folder(where setup.exe exists):
cd "C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\SQLServer2014"
setup.exe /Action=Uninstall /InstanceID=DENTALWRITER /Features=SQL /Q
(Legend):
/InstanceID=DENTALWRITER: Tells the installer exactly which instance to kill.
/Features=SQL: Specifically removes the database engine only. By omitting Tools, Conn, or SDK, you ensure your shared Management Studio and connectivity drivers remain for your other instances.
/Q: Runs it quietly to avoid the blank GUI screen you encountered.
2. Manual Service Deletion (If the above fails)
If the installer continues to claim there is "nothing to remove," it’s likely just a "zombie" service entry. You can delete the specific service for DENTALWRITER without affecting your other SQL instances.
- Open PowerShell as Administrator.
- Identify the specific service: Get-Service -Name "MSSQL$DENTALWRITER"
- Remove only that service: sc.exe delete "MSSQL$DENTALWRITER"
- Note: Other instances (e.g., a default instance named MSSQLSERVER or another named instance like SQLEXPRESS) will not be affected because their service names are different.
3. Cleaning the Instance-Specific Registry Key
To stop the DENTALWRITER name from appearing in setup menus or your migration scripts, you can remove its specific registry hive.
- Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL
- In the right-hand pane, look for the value named DENTALWRITER.
- Delete only that value. This unregisters the name from the SQL Server browser without touching the shared components used by your other instances.