Jump to content

Recommended Posts

Posted

So this year i'm planning to do a SIMS SQL migration from 2012 to 2016. I've installed SQL 2016 onto the same server as a different named instance ready for the migration.

From documentation i've read is seems fairly straight forward to do the migration and update the connect.ini files on the clients.

 

However, we probably have about 10 different bits of software on the server which link to SIMS to extract information.

 

Is there any easy way to ensure i change all programs which link into sims (as it will have a new instance name) or is it literally a case of changing them one by one?

Posted
You will find most will base their config on the connect.ini on the server. Once changed, hopefully you won't have as many to change manually.
Posted
well worth getting them all listed and then investigating the config options on each before you start - it'll avoid the screams when you forget to fix one of them and something somewhere doesn't work.
Posted (edited)

If you are using the migration tool you have the option of a 'redirect' on the SQL2012 instance. This is just a signpost on SQL2012 to point any request for SIMS to SQL2016. The advantage is that you don't need to update your connect .ini files or any other addon's, the con, is that you have to leave SQL2012 running in the background.

 

> You might want to change the connect.ini but still use the redirect so the addon's work. (edit)

Edited by Banjo

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...