Timeline for How to add new sysadmin account when no sysadmin accounts exist
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 16, 2021 at 17:22 | history | edited | Hannah Vernon♦ | CC BY-SA 4.0 |
added pointer for future visitors to take a look a the other answers.
|
| Jan 22, 2012 at 13:04 | history | migrated | from stackoverflow.com (revisions) | ||
| May 8, 2011 at 16:58 | comment | added | Mark D Jackson | Also, I did make a copy of the database files, but it turned out this was not necessary. The uninstall did not remove the databases. However, I would still recommend copying the database files just in case this behaviour is different on different versions of SQL server. | |
| May 8, 2011 at 16:56 | vote | accept | CommunityBot | ||
| May 8, 2011 at 16:51 | comment | added | Mark D Jackson | Thanks - I uninstalled the instance and reinstalled. Reattached the database and everything is fine again. A couple of things to watch out for were using the full database engine installer to reinstall the instance (I had a management tools only installer which stumped me for a while). Also you need to change the permissions on the database files so otherwise you get an error when attaching (error 5). Other than that - all worked fine. | |
| May 7, 2011 at 15:12 | history | answered | Damien_The_Unbeliever | CC BY-SA 3.0 |