SIMS migration - help needed!

[ndavies]

Hi there

As it was the weekend, I thought lets kick off the SIMS migration remotely. I'm currently half way through it and it was going swimmingly until when the SQL2005migration utility asks me for an sa password. None of us know it so we guessed it as blank. This prompts us for a database name BUT the list is empty...so I thought, ok maybe wrong password, I've since changed the sa password ...to an obvious choice..for now...and still the list is empty.

Capita posted the following, vague instructions

KB72251 - No database appearing in the dropdown box - Running the SIMS SQL Migration Utility

--------------------------------------------------------------------------------
Created 07/08/2007
Last Updated 07/08/2007


--------------------------------------------------------------------------------
Affected Products SIMS .net Installation & Upgrade

--------------------------------------------------------------------------------

Notes When running the Migration utility after entering the SA username and password
Click Connect
There is no database appearing in the drop down box.
--------------------------------------------------------------------------------

Advice Please close the Migration tool and then re-run the exe.


If the database still does not appear then you will need to do the following


Stop the SQL Server


Copy the SIMS.mdf and SIMS.ldf


Re-start the SQL Server


Remove SQL Server via Add / Remove programs


Re-name the Microsoft Sql Server folder to Microsoft SQL Server old (If there is more than one instance of SQL 2000 on the machine then you will need to re-name the MSSQL$SIMS folder to MSSQL$SIMSold)


Install a new instance of SQL 2000


Does this look advisable...I REALLY don't want to screw up SIMS for now
Any advice greatly appreciated

Nick

[tech_guy]

Whoa you're brave doing it remotely!

[ndavies]

LMAO
I'm sweating buckets...but it seems to have gone fine up to this point...

[ndavies]

...cue someone to say "Brave or Stoopid"

[ComeOnUOs]

Hi Nick

Try logging in to Sims and out again, then run the migration utililty again. Not sure why, but this worked for me

[ndavies]

AWESOME! advice here doesn't get any better! your advice fixed my issue. why is SIMS such an inconsistent and devilish beast to deal with...really frustrates me at times..

thanks for your help! it SEEMS to have worked...tomorrow morning is the pudding proving i guess....

[zag]

Do you need the SA password for the migration? I have no idea what that is!

[tech_guy]

Sims.Net Support at the LEA should have it on record for you.

[ndavies]

Our password turned out to be blank. Try this first and if it then moves onto asking what database you want to migrate, you've cracked it!

[ndavies]

..I changed the password now of course...

[apeo]

Wow remote migration.. i do alot remotely but i wouldnt even think of doing a major job like that remotely but im glad it was sorted in the end.

You dont need to contact your LEA as you can change the sa password yourself if you dont know what it is. Question is should i really announce in public? Im not sure but there may even be a thread that mentions how you reset the sa password. PM me if you want to know how to reset the sa password.

EDIT: Ok my post was late and you sorted it already. Its funny how the sa password is often blank.

[DMcCoy]

Just a note to keep an eye out if you use dbattach to automate backups, the september release seems to broken (for me), it was happily working with version 1.6 of dbattach but with 1.7 it won't accept any user I try as valid - including SA and the Administrator :|

[apeo]

Dont use DBAttach to do backups myself, i just stop the service altogether... Thanks for the warning tho.

[splattthecat]

Just a note to keep an eye out if you use dbattach to automate backups, the september release seems to broken (for me), it was happily working with version 1.6 of dbattach but with 1.7 it won't accept any user I try as valid - including SA and the Administrator :|

I have had confirmation from Capita that dbAttach (1.7.1) no longer works when trying to create backups using the SA login. This is currently being worked on.

[m2d2]

Dont use DBAttach to do backups myself, i just stop the service altogether... Thanks for the warning tho.

This was an OK plan up to August if you had the diskspace for copies or could control the backup window.

Under the new system passwords are tied to the RDBMS/server and not the database. So you may have to hand out new passwords o staff after a bare metal recovery or transfer to another server. Oh joy