[SIMS] Moving SIMS to new server

[jasonb007]

I want to move our SIMS to a new server as the old server is so old and slow. Also will be replacing my SIMS workstations, so basically, starting from scratch. I've done this before when SQL version was 2005 following excellent instruction from | SiX | Somerset Internet Exchange |. The existing server has recently been upgraded to SQL2008 so can't use these notes. I've tried in a test enviroment to setup but getting errors on the DBattach phase - Error ASSEMBLY dznet Does not exist, Please Run SIMSSQLApplicationSetup.exe.

I've started off by running the SIMS-FMS SQL2008.exe file, followed on screen prompts and changed the path to f:\program files\microsoft sql server etc.

Anyone done a move to new server using sql2008 and can point me in the right direction.

Thanks.

[jasonb007]

Jumped the gun a little, found the updated info !

Here for anyone else who needs to do it !

http://www.six.somerset.gov.uk/sixv3....asp?did=24645

[jasonb007]

Just confirming the above instructions do work ! Done a succesful migration today. Excellent guide !

[mtillbrook]

Hi
I am just moving SIMS to a SQL 2012 server and am getting a similar error.
The link above doesnt work any more - does anyone have a clue?

Cheers!

[Rawns]

Hi
I am just moving SIMS to a SQL 2012 server and am getting a similar error.
The link above doesnt work any more - does anyone have a clue?

Cheers!

Nice to see that our documents were securely locked down back then!!!!

@mtillbrook - I guess your migrating juts SIMS .net and FMS?

[TheScarfedOne]

Not sure on the SQL version compat with current sims versions. I think there is a similar thread about this too... @vikpaw?

[Rawns]

SIMS and FMS are now supported on SQL 2012 since the SIMS Autumn release if migrated across manually. However, both SIMS AND FMS HAVEto be on the same SQL version.

SOLUS3 and Discover are not yet supported on SQL2012.

[matt40k]

SOLUS3 and Discover are not yet supported on SQL2012.

Been told it's because the SOLUS3 and Discover use VSDBCMD to deploy\upgrade the SQL database, which doesn't support SQL 2012 and it's replacement, SSDT, doesn't work with XP\2003 - which explains why they've holding off till they drop xp\2003 support for servers. Shame they didn't do what they did with SIMS and keep the application and database logic separate.

[whitejames]

We are just setting up a new SQL 2008 R2 Server I did a restore of the SIMS db but it does not show the security/roles within SQL how do I get this to be brought across as I want to test a workstation on the new test Server.

[Rawns]

Sounds like they were not transferred before the backup. When we do a backup, we run these commands first to make sure they are included in the backup:

osql –S127.0.0.1\sims2008 -E -n -Q"exec sims.sims.db_p_transfer_login"

osql –S127.0.0.1\sims2008 -E -n -Q"exec ccsfms.sims.db_p_transfer_login"

Also, when we migrate SIMS to a new server, we run these commands, detach the database and copy it across, then re-attach it. We don't restore from a backup.

[whitejames]

It comes up with osql does not support all features of SQL Server 2008 R2. Use sqlcmd instead.?

[vikpaw]

detaching and reattaching on the existing server, will copy the logins / credentials into the db (like those transfer logins scripts). you can then take a .bak file over elsewhere and restore it. restore then pushes them back and makes them usable. i hate detaching the live server though, just in case it doesn't reattach.

[whitejames]

Thanks @vikpaw I will try this later today will have to kick users off to do this.

[vikpaw]

I did have a CR that asked for command line options to run those stored procedures from dbattach, but it got spring cleaned!
If you have sql management studio, you might be able to run it from there.

[LinkZ]

detaching and reattaching on the existing server, will copy the logins / credentials into the db (like those transfer logins scripts). you can then take a .bak file over elsewhere and restore it. restore then pushes them back and makes them usable. i hate detaching the live server though, just in case it doesn't reattach.

So you could just detach the database from the existing server, this will transfer the logins into the SIMS.mdf file, then attach the database on the new server and it will bring over all the SIMS logons? Does this work the same with the FMS database too?