One of our clients already has an extensive SQL server 2012 enterprise edition setup in place for their internal apps. They would like to continue using this for their Creatio instance as well. We are aware that Creatio supports 2012 SP 3 and higher. A few questions in this regard -
1. Would there be support for SQL Server 2012 in future versions of Creatio as well?
2. How easy/difficult is it to move from an older to a newer version of SQL Server in a working Creatio instance?
Like
Hello,
1. We already do not recommend using SQL Server 2012 for onsite deployment and use 2016 version instead.
2. It depends on the system administrator and server structure and many other variables that are hard to predict.
Best regards,
Angela
Angela Reyes,
Hi Angela,
Are there any known issues with Creatio on SQL 2012? The documentation says that Creatio is compatible with 2012 SP3 and higher.
M Shrikanth,
There are no known issues so far. If needed you may stay on SQL 2012.
Angela Reyes,
Thank you very much Angela. Appreciate your response. Quick follow up question -
Are there any known performance, security, availability or any other benefits at all, to Creatio using SQL 2016 instead of 2012? We want to understand if there are reasons why Creatio would recommend 2016. We would like to pass this on to our client to enable them to make a conscious choice to move to SQL 2016.
We need high availability, redundancy and fail over and are going with a web farm environment on a private cloud. Also, We will be using the Machine learning service in Creatio. Let me know if this makes any difference to the SQL version choice.
M Shrikanth,
We recommend SQL 2016 due to its own features that were implemented in that version, like security features, ect.
Best regards,
Angela
Angela Reyes,
Got it. Thank you Angela. So the Creatio application per say does not benefit from moving to SQL 2016. But owing to inherent advantages in SQL 2016, it is recommended.