Arcath Posted March 7, 2019 Posted March 7, 2019 Over half term I migrated SMS/FMS to a new server without any issues. I used SQL2017 and everything worked fine on the server and test client. Since half term FMS is throwing up various SQL errors. The annoying thing is that the problem seems to be intermittent. I spent a coupleof hours working on a client on Tuesday, got an email Wednesday saying it was working fine and then today (Thursday) I've been told it hasn't worked at all this morning. Due to the time of year the school desperatley need to get into FMS all the time and they've done too much work in it for us just restore the pre-migration backup. Has anyone got FMS working on SQL2017? Did you need to make any changes to the SQLServer config? Did you need anything installing on the clients? On the other end of the scale, does anyone have a way to attach SQL databases to older versions of SQL? I can't get the whole database to export through SSMS, and the tables/data only export is killing SSMS when I try to import it.
Banjo Posted March 8, 2019 Posted March 8, 2019 From the looks of it - you are a bit ahead of the game. It's not on Capita's radar as yet. You could try SQL 2016 SP1 in the meantime.
Arthur Posted March 8, 2019 Posted March 8, 2019 It's not on Capita's radar as yet. Windows Server 2019 is missing too. I think Capita need a new radar!
Banjo Posted March 8, 2019 Posted March 8, 2019 (edited) Windows Server 2019 is missing too. I think Capita need a new radar! Capita working at the very cutting edge of technology ! SQL 2016 SP2 is missing from the roadmap as well. Edited March 8, 2019 by Banjo 1
JTP Posted March 8, 2019 Posted March 8, 2019 I think you will find that Capita support for SQL with stop with 2016. I believe that there is talk of them making SIMS support native SQL 2016 rather than setting a compatibility mode. I also think there is talk of not supporting office 2019 either, this being that last version to be an installable. This in view of the fact that the fabled SIMS primary will actually be available and usable before MS support for SQL 2016 & Office 2019 run out.
Banjo Posted March 8, 2019 Posted March 8, 2019 I think you will find that Capita support for SQL with stop with 2016. I believe that there is talk of them making SIMS support native SQL 2016 rather than setting a compatibility mode. I also think there is talk of not supporting office 2019 either, this being that last version to be an installable. This in view of the fact that the fabled SIMS primary will actually be available and usable before MS support for SQL 2016 & Office 2019 run out. I think Office 2019 and future SQL releases will be needed for the secondary market even if SIMS8 comes to the primary sector in the next 18 months.
TwistedHelixis Posted March 8, 2019 Posted March 8, 2019 When you migrated did you use the Capita migration tool? or just install the new SQL version and import the database? The tool gets the database ready for the new version.
krtek Posted March 8, 2019 Posted March 8, 2019 Capita are consulting with schools and support teams and are to publish an updated roadmap in the coming weeks - this will set out the plans to adopt new technologies At the end of the day it's hugely expensive and problematic to test against all of the various combinations of platform in use in schools and we all know that schools which want to hold on to legacy systems as long as they can removing support for Windows 7 and requiring that 20,000 schools move to office 2019 to use the next release of SIMS for instance would not be popular whilst I would accept that they need to respond to the needs of schools they are listening - please ensure that you speak to your support unit when considering your replacement programmes so that your views are reflected Dave Dave
Arcath Posted March 8, 2019 Author Posted March 8, 2019 When you migrated did you use the Capita migration tool? or just install the new SQL version and import the database? The tool gets the database ready for the new version. I used dbattach to attach the FMS database to the new instance which does run a load of routines to prepare the database. The idea I have in the back of my head is to export all the data out of the database and import it over the data in a backup which will hopefully create a version that can be used on lower versions.
TwistedHelixis Posted March 8, 2019 Posted March 8, 2019 I used dbattach to attach the FMS database to the new instance which does run a load of routines to prepare the database. Yes but it is the migration tool that you should use if you are moving between different SQL versions, or so I have been told.
Banjo Posted March 8, 2019 Posted March 8, 2019 Yes but it is the migration tool that you should use if you are moving between different SQL versions, or so I have been told. If SQL2017 isn't supported, then the migration tool would probably have failed. You could try running SQL 2017 in compatibility mode with 2016. Capita advised this with SQL 2014 > to run as SQL 2012.
Arcath Posted March 12, 2019 Author Posted March 12, 2019 Has anyone got a copy of the SQL migration tool I can have?
matt40k Posted March 12, 2019 Posted March 12, 2019 Has anyone got a copy of the SQL migration tool I can have? Sure, my mate Capita has a copy they'll happily send you. 1
Esteban_Child_of_the_Sun Posted March 12, 2019 Posted March 12, 2019 FYI: The migration tool will currently only work with SQL2016 SP1 so make sure you don't use anything more recent than that
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now