April 29, 2015 at 8:10 am
I have a server running SQL 2008 r2. It is being repurposed, but because of the SQL licenses, I didn't want to wipe the machine and do a fresh install.
With that being said, the machine predates my tenor here and I do not have the credentials to log on to the database engine. The database it was installed to run never went into production.
I would like to reuse the license to run an instance of VoCollect's Voice picking software/database.
How can I either reset the password to gain access? Or, can I reinstall and somehow pull the license(s) (cals) from the machine before I uninstall/reinstall the software?
Any help with this would be greatly appreciated.
Thanks,
-AD
April 29, 2015 at 9:21 am
licenses are administrative. No checking here, so just install on a new machine, use the license, and decommission the old one so that you don't get caught in a licensing issue if you were to be audited. I've only been once in 25 years, but it has happened.
Alternatively, start the server in single user mode and log in locally with the DAC as a Windows Admin. You can then reset sa.
April 29, 2015 at 9:37 am
Installing on a new machine isn't really an option because I only have 2 other servers. They are both running other sql databases for SBS, and backupexec and for Retalix order entry/online order entry.
I have tried logging in using the network admin account and I am not able to make the credential changes. Is there somewhere I can find instructions for this? Perhaps I am overlooking something.
A second set of eyes would be PRICELESS! ha
April 29, 2015 at 9:44 am
I found the instructions for changing the sa password, and it worked for the local database instance, but I am not able to get onto any of the other database instances to change it for them.
Thoughts?
April 29, 2015 at 9:52 am
Not sure what you mean by local v others.
You need to be on the console, not on a different machine.
April 29, 2015 at 10:03 am
I show 3 databases available to connect to:
(Local) - This database had the password stored so I was able to get on it and change it as I needed.
AFSSERVER - the test software we dropped. I would like to disconnect this database and remove it completely from the physical server.
sqlserver - ?? - Remove this from the physical server as well.
April 29, 2015 at 3:13 pm
Are these databases or instances? There's a big difference.
April 30, 2015 at 6:38 am
Your absolutely right.... my mistake. Instances.
April 30, 2015 at 10:20 am
For the named instances, you should be able to uninstall any of them from setup. You could just delete the binaries and registry stuff, but that's a pain to dig out.
If you don't care about the clean server, here's what I'd do.
- stop the services (db service and agent service) for those instances. Set them to manul
- Copy any .mdf/ldf/ndf files for those instances to an archive. Keep a couple copies in case you find you need them.
- Delete the user mdf/ldf/ndf files from the server.
- delete old backups, log files, audit files.
The binaries and system dbs typically aren't enough space to worry about.
If the names of the named instances don't matter, it doesn't hurt to leave things. If they're off, the license can be re-used elsewhere.
April 30, 2015 at 1:07 pm
Awesome thanks for the help!
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply