Reset Search
 

 

Article

CCH Central : Retirement of Microsoft SQL Server2008 & 2008 r2

« Go Back

Information

 
Article No:000010169
Question
I'm preparing to update my Microsoft SQL Server 2008 / 2008 r2 ahead of the end of life on 9th July 2019. Are there any frequently asked questions that I should be aware of?
Answer
Below is the list of FAQs based on queries from our client base:
 
Question: How do I check what version of Microsoft SQL Server is hosting my CCH Central database(s)?
Answer: Knowledge article number 11072 explains how to do this.

Question: Can I update to the latest version of SQL Server?
Answer: Only if you are running an operating system supported by it. SQL Server 2016 and 2017 are incompatible with earlier versions of Windows, such as Windows 7.
 
Question: If I cannot update to SQL Server 2017 then what is the next best version?
Answer: SQL Server 2014 Express is the version we currently ship in the Central Suite Installer. For maximum compatibility with the currently supported Windows operating systems, this is the next best option.
 
Question: Can I go straight from SQL Server 2008/2008 R2 to SQL Server 2017?
Answer: Yes, if you are running SQL Server 2008 R2 with SP3 then you can upgrade straight to 2017. You may encounter an issue with the installation of the new Full-Text Engine service when making such a significant jump between SQL Server versions - from 2008 to 2017. In this case, you should contact Microsoft to ensure that the upgrade from 2008 to 2017 is supported from a Full-Text engine perspective.
 
Question: Do I need to install any service packs, cumulative updates or general distribution releases once I have migrated to a newer version of SQL Server?
Answer: Yes, you must service the version of SQL Server you are running to bring it up-to-date. Depending on the version you migrate to, this will either mean a combination of service pack, cumulative update and general distribution release, or just cumulative release and general distribution release. Microsoft has changed their servicing model for SQL Server 2017 and no longer produces service packs. You can find all of the latest information in this area at:
 
Question: Do I also need to update the local workstation installation where I am using travelling functionality?
Answer: Yes, the local instance must also be upgraded to a supported version of SQL Server. If using a network installation share to deploy the workstation components, you will also need to update the SQLSetup.exe package in the CentralLoaderClient SQLSetup directory.
 
Question: Does Microsoft produce any collateral for assisting in the upgrade of SQL Server 2008/2008 R2?
Yes, the following links provide a comprehensive set of resources in this area:

https://docs.microsoft.com/en-us/sql/database-engine/install-windows/choose-a-database-engine-upgrade-method?view=sql-server-2017

https://docs.microsoft.com/en-us/sql/database-engine/install-windows/upgrade-sql-server-using-the-installation-wizard-setup?view=sql-server-2017

https://www.microsoft.com/en-gb/sql-server/sql-server-2008

Question: Which databases do I need to backup before running an in-place upgrade of SQL Server?
Answer: You must have a backup for all user databases hosted by the instance being upgraded and in the case of Central and Document databases, they must be time synchronised to ensure they backups are compatible. Depending on the Central modules you are licensed for this may be the following two sets:
 
  • Central, Document, CCHBackup
  • Central, CCHBackup
  • VPMSER, Document, CCHBackup
  • VPMSER, CCH Backup
  • If you are a Trust Accounts user then you will also need to include the Trust Accounts SQL Database in the backup set if you are running Trust Accounts in conjunction with a SQL Server-based backend
  • If you have legacy CCH products hosted by the instance you are upgrading then you will also need to backup these databases too
 
Question: How long should an in-place upgrade take?
Answer: This is dependent on the performance of the computer where the SQL Server program is located. Excluding database backup time, the operation may take anywhere from thirty minutes to several hours. On this basis, ensure this operation is only performed during a suitable maintenance window where the total system downtime can be managed.
 
Question: SQL Server 2017 has a new CLR security feature called CLR Strict Security. If I am migrating to SQL Server 2017 what do I need to do?
Answer: CLR Strict Security needs to be deactivated once you have migrated to this version. This can be done using a script.
 
Question: If I am running the Document database in a separate instance called CCHDOCUMENT do I also need to upgrade this instance?
Answer: Yes, if the SQL Server version hosting the Document Database is 10.x or 10.5.x then it will also need to be upgraded to a later version of SQL Server.
 
Question: What are the end of life dates for all SQL Server versions currently supported by Microsoft:
Answer: The following chart contains this information:
 
SQL ServerEnd of Support (extended)WKUK End of Life
SQL Server 200809/07/2019As Microsoft
SQL Server 2008 R209/07/2019As Microsoft
SQL Server 201212/07/2022As Microsoft
SQL Server 201409/07/2024As Microsoft
SQL Server 201614/07/2026As Microsoft
SQL Server 201712/10/2027As Microsoft
 
Question: Can I perform an in-place upgrade using a configuration.ini file to make use of the Advanced installation features of the SQL Server Installation program?
Answer: Yes, information on building a configuration.ini file can be found at:
 
  • Use of a configuration.ini is useful in cases where you need to upgrade multiple instances, as in the case of a set of computers running a local installation of CCH Central, and therefore SQL Server, for use in facilitating our travel functionality. Building an ini file allows for a repeatable process to be deployed to reduce the user input required by the installation wizard.

Question: Will Wolters Kluwer assist me in upgrading my SQL Server version?
Answer: Yes, please contact your Account Manager to obtain information on the additional service you may purchase for managed SQL Server upgrade assistance.
 
Question: What happens if my attempt to upgrade to a later version of SQL Server fails?
Answer: At the first instance you should seek the assistance of your local IT provider to facilitate the restoration of your system to a time before the upgrade was performed, making use of the user database backups you have secured before the operation was initialised. Wolters Kluwer can assist in the restoration of your system but the assistance would only be provided on a chargeable basis and there is likely to be a delay in securing time with the Technical Services Team which may vary from days to weeks. The Technical Services Team prioritise the servicing of existing scheduled jobs. We cannot predict when the assistance will be available unless their services have been secured in advance.
 
Question: Are there any plans to add functionality to the Central Suite Installer to facilitate the upgrade of the database platform for those sites running a version of SQL Server Express deployed by an initial installation of the CCH products?
Answer: There are no plans to add this functionality to the suite during 2018 but we are investigating the option of adding this functionality at a later date. To ensure you upgrade to a supported version of SQL Server before July 2019 you should plan on the basis that this functionality will not exist in the short-term.
File Attachment 1 
File Attachment 2 
File Attachment 3 
File Attachment 4 
File Attachment 5 

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255