SIMS Migration help

[randle]

I have previously installed SQL Express and converted all instances other than SIMS over to this (ie. Backup Exec, Sophos, WSUS 3).

 

When running the migration tool i get to the "Select and connect to your SQL2005/SQL Express Database Server" screen but from the drop down box this only gives me the option to choose one of the Three instances that already exist ie. SERVER01\MICROSOFT##SSEE, SERVER01\BKUPEXEC and SERVER01\SOPHOS

 

Surely i don't select one of these as they are already being used!! A little help would be magic 8O

[Jake]

Daft though it may sound, try logging into SIMS on the server, then log out of sims and then run the migration tool again.

[randle]

It's not the SQL 2000 instance i'm trying to find (SIMS shows up fine here) it's the next screen where it's asking to select a SQL Express database server to connect to which surely would just be "SERVER01"!!?

 

Anyway i tried you suggestion but this has changed nothing. Am i missing the picture here?

[Jake]

Ah...my bad, I misread the post

 

yeah, when I did ours on Tuesday, it just showed "SIMSserver\SIMS2005" , so I imagine you are right, yours should show SERVER01\whatever

[randle]

I forgot to add that i unticked the "Install a new SQL Express Instance to host SIMS" box as the istructions state that this should be delselected if you already have an installation of SQL Server 2005 present. Should i really tick this?

[Jake]

Not sure on that one, as we didnt already have an SQL Server 2005 installation present, so we left it ticked of course

[Hecate]

I think you are confusing instances and databases. Each instance can contain more than one database so you can add the SIMS database to an existing instance or create a new one depending on your set up. On ours which is full SQLServer 2005 we have the library database and SIMS on the same instance.

[randle]

Hecate: I thought this first tick box meant the initial install of SQL Express on the server which i had already done. I thought a new SQL Express Instance meant a complete seperate SQL install (I'm new to getting my hands dirtier with SQL so don't laugh)

 

I just bit the bullet and ticked the Install a new instance. This has gone through and migrated as expected so i'm one step closer.

 

When logging in i now get an error saying "Invalid User Name/Password". I'm definately using the correct username/password so what's going wrong here?

[randle]

Anyone? I'm getting a little desperate here as No-one can use SIMS currently. Aren't i going to be popular

[jcollings]

Anyone? I'm getting a little desperate here as No-one can use SIMS currently. Aren't i going to be popular

 

Have you checked what your s:\sims\connect.ini says and what your connect.ini on your workstations say? I had this problem.

 

Should say something like

 

\\Servername\instance

DATABASE=SIMS

[Oops_my_bad]

Have you made sure you aren't using trusted logins but instead just using SQL authentication only?

 

Failing that do you have a trusty backdoor account into SIMS that you can reset your SIMS password via system manager with?

[randle]

@jcollings: My SIMS\SIMS\connect.ini file has

[sIMSConnection]

ServerName=SERVER01\SIMS

DatabaseName=SIMS

 

and my Program files connect.ini has

[sIMSConnection]

Redirect=S:\SIMS

 

@TeddyKGB: How do i make sure i'm not using trusted logins?

 

No users i try can gain access

[jcollings]

@jcollings: My SIMS\SIMS\connect.ini file has

[sIMSConnection]

ServerName=SERVER01\SIMS

DatabaseName=SIMS

 

and my Program files connect.ini has

[sIMSConnection]

Redirect=S:\SIMS

 

 

The workstation on is fine. Your server one looks wrong to me.

 

Ours before conversion was

 

[sIMSConnection]

ServerName=SERVERNAME\SIMS

DatabaseName=SIMS

 

When I upgraded I changed it to

[sIMSConnection]

ServerName=SERVERNAME\SIMS205 (new instance name)

DatabaseName=SIMS

 

That sorted that issue for me. Out of interest it you logon to the SIMS server itself and try to run SIMS do you get the same result?

[randle]

I've changed the servername to the new instance which i'm sure was going to work but this made no difference unfortunately.

 

It's the server i'm trying to run this on

[randle]

Just been speaking to Capita and none of the data has been migrated over even though the migration tool said it had completed successfully!! I'm wondering whether this is because originally i had the full version of SQL 2000 and am trying to migrate to the free version!!?

 

I have also checked the instances i'd installed for Backup Exec & Sophos and it looks like these haven't migrated accross either. Is there a special migration proccess needed for these aswell?

 

Anyway we're back up and running on SQL 2000 (Lucky i didn't uninstall) and have been told to try the migration again but i don't hold much hope for this.

[DMcCoy]

You don't have Backup Exec, sophos and sims attached to the same instance do you? I hope they are in seperate databases at least! The problem with the sql express and msde instances that come with software are usually quite happy to remove the whole thing if you modify/ununstall the application taking your other databases with it.

 

I assume you are reading the sql migration guide? Your other databases will be an issue if they are not seperate instances as they might not even work with 2005!

[randle]

These all have seperate instances. When I first installed SQL Express and transfered Backup Exec and Sophos over, i ran the installer on each occasion so that a seperate instance was installed for each one.

 

I have checked the SQL Server Configuration Manager and all seems fine with a seperate instance for each application.

 

I am reading the migration guide. I wouldn't dare try without it seeing as i'm by far a maestro with SQL

[randle]

I ran this again today and this time it's migrated fine so looks like it wasn't too happy about installing an instance and migrating at the same time for some reason.

 

Anyway thanks for the help