SQL 6.5 SA Password Issue

  • Okay yep i can look in the registry and see the Supposed SA "password" but it doesn't work for any tools, Security manager, Isql, etc. I have tried anything and everything. I'm deathly afraid to reset the password cause there are a zillion jobs using that account. I inherited this NT4 Server with SQL 6.5, with a Corporate Application that would be catatrophic if it died. I am in between the rock and a hard place. anyone got any ideas????

    its still kicking out backups (both fulls and transaction logs, so would it be better to just create a new virtual server, install SQL 6.5 and restore the data there and rename the virtual server the same as the current antique hardware server name???? And do you think i can trick the application to use a new platform instead of NT4 Server????

  • I do not think changing sa password will affect your scheduled jobs.

    The failure of your jobs may have some other reasons. Check SQL logs and see whether or not you can find any clue.

    If necessary, you can add a log output file to help you get detail information.

    SQL 6.5 is old. I have not used it for years.

  • I am not sure I understand what you are asking for help with.

    Are you asking for help with finding or resetting the SA password?

    Are you asking for help with how to upgrade to a newer version of SQL Server?

  • okay i guess i need to outline the whole picture. its on a Dying server, there is not enough space on the server for backups so they are being sent to another server. i already tried to install a new instance of 6.5 on a new virtual server and recover the backups there. it failed miserably no matter what i tried. So the backups are no good it would seem. so i guess i am left with resetting the SA password, hopefully making a good backup somewhere. ( the jobs are old jobs that send data all over, and i mean REALLY old jobs) most are running under accounts that i have no way to recover the passwords for. just a mess, and i know once i start down the path, i'm going to get burned.

  • What do you mean that recovering the backups failed miserably? What errors are you receiving or issues are you facing? I agree, I haven't used 6.5 in years but I don't recall issues with backup/restore procedures. That would be my first concern - valid, usable backups. If your current hardware fails, your dead if what you stated is true. I don't believe the sa password is going to fix the backup issue you claim to be having, there is more to this. Provide more detail so we can try and help.

    -- You can't be late until you show up.

  • There used to be issues with knowing the proper device sizes in 6.5 for some restores.

    How is the server dying? Can you not add disks? That might be the easiest thing to do.

  • william.ring (5/1/2008)


    okay i guess i need to outline the whole picture. its on a Dying server, there is not enough space on the server for backups so they are being sent to another server. i already tried to install a new instance of 6.5 on a new virtual server and recover the backups there. it failed miserably no matter what i tried. So the backups are no good it would seem. so i guess i am left with resetting the SA password, hopefully making a good backup somewhere. ( the jobs are old jobs that send data all over, and i mean REALLY old jobs) most are running under accounts that i have no way to recover the passwords for. just a mess, and i know once i start down the path, i'm going to get burned.

    Do you have experience with doing restores of SQL Server 6.5 databases? It is a lot different than doing restores on later versions of SQL Server. You have to setup devices on the server that you want to restore to that match the size of the devices on the old server. This is really only a job for someone with significant experience with SQL Server 6.5, but the process is documented in the SQL Server 6.5 Books Online if you really want to try.

    You may better off doing an upgrade to SQL Server 2000 using the SQL Server 2000 Upgrade Wizard. The procedure for doing this is documented in SQL Server 2000 Books Online. Once you have a SQL Server 2000 version, you can upgrade that to SQL Server 2005 if you want.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply