Re: sa password was inadvertently changed. With a kicker...
From: Kevin (ReplyTo_at_Newsgroups.only)
Date: 08/08/03
- Next message: iggy: "Re: MS03-31Breaks MOM?"
- Previous message: Bill R.: "Re: MS03-031 & missing SQL performance counters"
- In reply to: Denny: "Re: sa password was inadvertently changed. With a kicker..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 8 Aug 2003 06:44:04 -0700
4) is not a last resort, that should be SOP - rebuild master, restore from
backup prior to "Corruption" by vendor script. You will lose all config and
login changes since the backup.
-- ---------------------------------------------------- The views expressed here are my own and not of my employer. ---------------------------------------------------- "Denny" <mrdenny@gamespy.com> wrote in message news:#K8dVcUXDHA.2592@TK2MSFTNGP09.phx.gbl... > I see four possible options for you. > > 1. Use some other account that the client has (any domain admin should have > sysadmin permissions unless BUILTIN\Administrators has been removed) and use > sp_password to change the sa password (see BOL). > 2. Call the vendor of the new software product, and ask them what the > install script sets the SA password to when installing the product. > 3. Did around there install package, and see if the sql script that changed > the password happens to be there. If it is the password will be in it. > 4. (Use this as a last resort, no idea if it will actually work). Detach > all user databases, and move them somewhere save (another drive, another > folder, another machine, etc). Then restore the master db from a backup > that was before the sa password was changed. Then delete all the suspect > databases that are listed. Put the database files back where they should > be, and reattach them. > > No mater which one you use, be sure to set the sa password once you can get > into the system with sysadmin permissions. > > Good luck. > > -- > Denny Cherry > DBA > GameSpy Industries > "Ryan Gaudet" <rgaudet@hushmail.com> wrote in message > news:030501c35d2f$84266260$a501280a@phx.gbl... > > Hi, > > I have a SQL Server 7 Standard edition server running in a > > clients IT environment. Sometime last week, the IT > > department installed a new application that needed a new > > SQL server database that was to be installed on a > > different SQL Server. When they were prompted to select > > the server to install the database to, they inadvertently > > installed to our server. (our sa password was blank and > > that's how they could do this....Very bad, I know)The > > script that created the database reset the sa password and > > noone seems to know what it is. > > Here's the kicker; When we installed the SQL server, it > > was part of domain "A" and we were logged in as a service > > account user as per our application requirements but the > > client installed a new PDC last spring and we moved the > > server to the new domain so the account we used to install > > the SQL server doesn't exist so we don't have an account > > with admin rights. We tried setting up a bogus PDC with > > the old domain name, setting up a trust between the > > domains and logging in with the original account name to > > see if we could trick it that way but to no avail. > > Is there any way that we will be able to reset the sa > > password or change the domain reference to the NT user > > account with admin priveledges? If not, will Microsoft be > > able to reset the sa password? I know it will cost money > > if they can but we need to get this resolved. > > > > Thanks in advance. > >
- Next message: iggy: "Re: MS03-31Breaks MOM?"
- Previous message: Bill R.: "Re: MS03-031 & missing SQL performance counters"
- In reply to: Denny: "Re: sa password was inadvertently changed. With a kicker..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
