SIMS 2016 Migration Tool - Install SIMS Server on Destination or not?

[LazyD]

Hi,

 

Am currently doing a SIMS server migration from an old server and domain that was using SQL 2012 to a new server and different domain that has a waiting installation of SQL Server 2016 Standard.

 

The tool has detached and got the SQL databases out as bak files from the old server. As far as I can see there is no mention of how the SIMS server components should be set up on the destination server. I mean things like the SIMS shared folder (containing Setups, etc) and the ini files.

 

Considering that running the SIMS Installable main release (2013) normally installs an SQL Express instance (which I don't want), whats the method for getting SIMS on this new server? There seems to be no mention of this scenario in the 2016 migration tool documentation, it just talks about the detaching and attaching operation.

 

Do I need to manually create the relevant folders in the new share on the new server (copying the SIMS folder over from the old server)?

 

Then manually edit the ini files?

 

Thanks

[oododkodkdo]

You would need to contact your LA

[Banjo]

Hi,

 

Am currently doing a SIMS server migration from an old server and domain that was using SQL 2012 to a new server and different domain that has a waiting installation of SQL Server 2016 Standard.

 

The tool has detached and got the SQL databases out as bak files from the old server. As far as I can see there is no mention of how the SIMS server components should be set up on the destination server. I mean things like the SIMS shared folder (containing Setups, etc) and the ini files.

 

Considering that running the SIMS Installable main release (2013) normally installs an SQL Express instance (which I don't want), whats the method for getting SIMS on this new server? There seems to be no mention of this scenario in the 2016 migration tool documentation, it just talks about the detaching and attaching operation.

 

Do I need to manually create the relevant folders in the new share on the new server (copying the SIMS folder over from the old server)?

 

Then manually edit the ini files?

 

Thanks

 

The 'Migration Tool' is designed to upgrade the SQL databases to a newer instance. What it wont do is move the whole SIMS installation on the old server to the new. If you were installing a newer version of SQL on the old server then the Migration Tool is the way to go. Moving to a new server, then it's pretty much a waste of time as there is quite a bit more stuff to do than what this tool can offer.

[LazyD]

Ok. The migration tool documentation has a specific section all based around my scenario, moving to a new server.

 

So if you would not recommend the migration tool in my scenario, what procedure would you recommend? Install SIMS manually on destination server, uninstall SQL Express instance, install SQL Standard and attach databases?

[IrritableTech]

I would recommend using the migration tool to move your SQL. If memory serves the documentation does explain you have to run the process twice - once to extract and update the database, then on the new server to import it? I'm afraid it has been a while since I have done this.

 

I think there is capita documentation available for installing the core packages onto a new server too. It involves running the installer for the version of sims you are using (you can extract this from Solus3) and ensuring the 'this will be the server tick box is ticked. There are a few places you need to ensure are set correctly for your new server - the DMS folder for example. You can copy the content from the old server but the path must be updated to include the new server name for example.

 

Jump on the capita support site and do a lot of reading - I ended up getting info from a few documents and writing down my expected steps - which seemed to work fine. This was a while ago though, and I didn't have to do Solus3 or discover at the time.

 

By using the upgrade and extract tool remember that your old server is basically untouched (as long as you stop SQL afterwards to stop anyone getting in!). If the new install doesn't work you can fire up the old one and think again.

[Banjo]

Ok. The migration tool documentation has a specific section all based around my scenario, moving to a new server.

 

So if you would not recommend the migration tool in my scenario, what procedure would you recommend? Install SIMS manually on destination server, uninstall SQL Express instance, install SQL Standard and attach databases?

 

You will need to install SQL manually (or own script) on the new server as you are running Standard rather than Express. Also worth dropping on SSMS as well. The migration tool moves the database(s) across, but all its saving you doing in running Dbattach on the old server then on the new. The migration tool is good at upgrading instances (on the same server) where it can attach a redirect to the old instance, pointing at the new instance to save editing the connect.ini file.

 

However, for a new build you will need Borland & MSXML installing manually from the 2013 installers. Copy the old folder structure across to the new server (for CTFs and other files).

 

On top of this you then have to install and setup DOCServer and migrate the old to the new, install SIMS Service Manager and Discover (if you use it). Then drop on Solus 3 to get the updates from Capita/LA.

[ajp233]

Did this a couple of weeks ago. Detached the SIMS DB mdf/ldf from the SQL instance on the old server and copied them across to the new server. On the new server installed SQL 2016. Rebooted the server. Ran the SIMS 2013 installable release - it allowed me to pick the 2016 instance and attach the SIMS DB. Once completed I ran the Summer upgrade on the new server. Finally copied across the DOCSTORAGE folder from the old server to the relevant place on the new server.