SQL 2016 install - Two features I am not sure about during the setup

[TwistedHelixis]

Just testing in a vm migrating from SQL 2012 to SQL 2016. The database is just for SIMS & FMS

 

I am actually using my old notes from installing SQL2012. There are 2 features I am not sure about as 2012 did not list them.

 

R Services (in-Database)

PolyBase Query service

 

Do I need these features?

This is just a small primary school and I do not really want to select an option if it is not needed.

 

Cheers :0)

[mrwoberts]

Out of interest, are you using the latest migration tool from MyCapita Downloads section - they have a 2016 migration tool.

I'm considering this as a summer project, so I'm interested in your mileage with this one.

[TwistedHelixis]

Out of interest, are you using the latest migration tool from MyCapita Downloads section

 

I will be using the migration tool by Capita, but I have downloaded it from my Local Authority as our support is with them. The migration tool has always been simple to use and normally SQL is OK.

 

I will let you know how it goes when I find out about the SQL features I need or don't need.

[TwistedHelixis]

Well it turned out I had the full version of SQL and not the express version. Installing the express version does not even list those features.

 

Just installing on a test vm and will then test a migration of Sims

[mrwoberts]

Ah, thanks for that. I too will be using the Express version. I vaguely remember that the Capita tool adjusts the instance settings to better handle a SIMS db - not sure what settings, but I remember reading about it somewhere. Possibly memory related??

[TwistedHelixis]

Just finished a test migration and I notice that the Solus3 database is still on our old SQL2012 system. Any idea how I move this over to SQL2016?

[TwistedHelixis]

In addition, FMS does not load and gives an error about username or database name being wrong - giving up for a few days

[TwistedHelixis]

Just managed to get FMS running, I needed to update the fmsconnect.ini in the S drive.

 

Should this not get updated automatically?

 

Next I need to workout why Solus3 is still listing the old database for the clients and also how to move Solus to the new database.

 

Will probably create a new post and ask

[mrwoberts]

Just finished a test migration and I notice that the Solus3 database is still on our old SQL2012 system. Any idea how I move this over to SQL2016?

 

Had the exact same problem a while ago. I even posted a thread on here (that I can't find now), asking how I transfer the SOLUS db over. After manually copying the db over the Deployment software would simply not load - demanding that it couldn't connect to the 'old' db. Trawled through configuration files for Solus and I came to the conclusion that it must be coded somewhere that I can't edit. Gave up and just left the old DB running until I could be bother recreating a new one - which I still haven't done.

 

I'd personally love to know the answer to this - it's kept me awake at night for the past four years

[TwistedHelixis]

I'd personally love to know the answer to this - it's kept me awake at night for the past four years

 

Did you ever get it migrated. I managed to get mine migrated today :0)

[mrwoberts]

Whaaaaaaaaaat!

 

Come on bruv, spill the beans. How did you do it?

[TwistedHelixis]

Whaaaaaaaaaat!

 

Come on bruv, spill the beans. How did you do it?

I'll post some steps later :0)

[TwistedHelixis]

PM sent, so you can check my instructions before I post