0
I am currently trying to make live an SQL database which was originally created to store information for an old software called 'Primus 2.0'.
I have the files for the SQL instance (an MSSQL11 database) within C:\Program Files\Microsoft SQL Server, but as far as I can tell from my pokings in SQL Server Cofiguration Manager 2017, or the SQL Server 2017 Management Studio this SQL database is not live anywhere, however due to inexperience I do not know if this is possibly because it is an MSSQL11 instance.
There is an install of MS SQL Server 2012 but I think this has lost it's validity during a previous OS migration - it is not operational as it asks for SQL Server 2012 installation media before nearly any process.
In order to again host the database from the machine I tried running C:\Program Files\Microsoft SQL Server\Binn\sqlservr.exe but I get a message saying that:
Your SQL server is either corrupt or has been tampered with (Error getting instance ID from name). Please uninstall and then re-run setup to correct this problem.
Based upon the review of this issue I also tried running from cmd.exe with the -sSQLEXPRESS flag to no avail
In summary, is there a way to detect whether I actually have a live database on the machine currently given in doesn't show up in the management studio?
Also is there a way to uninstall this SQL instance and re-install based upon the instructions of the error message I have listed above? I cannot see any .msi or .exe files which look like they are for these tasks within the directory.
Scott Anderson
Posted 2019-03-28T17:57:20.963
Reputation: 115
You'd don't normally run sqlservr.exe directly. There should be a Windows Service for it called "SQL Server ...". You'd start that to run it. If there really is no installation to go with the database files then you'd probably be best just taking the mdf and ldf database files and moving them to the new SQL Server 2017 installation data folder and reattaching them. https://docs.microsoft.com/en-us/sql/relational-databases/databases/attach-a-database?view=sql-server-2017 you'll still have to fix the users and security afterwards.
– pholcroft – 2019-03-29T16:14:15.067