Pros and Cons of using Pega Marketing product/framework and SQL Server Database
Hi All,
Pega v7.3.1 is supported on Microsoft SQL Server 2016.
Pega Marketing 7.2.1 is not supported by Microsoft SQL Server 2016.
If we consider Pega Marketing 7.2.1 instead of Pega Marketing 7.31 in Pega Product v7.3.1 with SQL Server Database, will the functionalities related to the Pega Marketing 7.2.1 will be working as expected in Pega V7.3.1?
If we take the clone of lower version of Pega marketing and moving into the pega environment v7.3.1 and SQL Server 2016. Is it feasible to proceed with this setup?
Any suggestions?
Regards
SVA Quest
***Edited by Moderator Marissa to update platform capability tags***
Accepted Solution
Hi,
I am not sure what is the end goal here. Are you planning to eventually upgrade PM to 7.31 as well?
wrt built-on application layer, I am not sure how this is relevant here. when you upgrade to PM 7.31(which is the version that you can use with Pega 7.3.1), the changes that makes it compatible with sql server will also come in, you just have to make sure that your Application is built on "PegaMarketing_FW 07.31".
Hi
I dont think PM 7.21 is compatible with Pega 7.3.1.
PM 7.21 is compatible with Pega 7.2.2 with additional PM 7.21 hotfixes.
hence I think there will be errors if you start using PM 7.21 on Pega 7.3.1.
but if this is part of upgrade steps, its ok, as you have to upgrade the Pega to 7.3.1 first then run the upgrade of PM 7.21 to PM 7.31.
Hi Manu,
Thanks for the detailed inputs.
When we take the clone of PM v7.21 from the lower version, then the built-on application layer will remains same. Do you still observe any blockers in this approach (expect the DB compatibility issue)?
Regards
SVAQuest
Accepted Solution
Hi,
I am not sure what is the end goal here. Are you planning to eventually upgrade PM to 7.31 as well?
wrt built-on application layer, I am not sure how this is relevant here. when you upgrade to PM 7.31(which is the version that you can use with Pega 7.3.1), the changes that makes it compatible with sql server will also come in, you just have to make sure that your Application is built on "PegaMarketing_FW 07.31".
Thanks Manu for quick response.
Agreed. But consider it “as-is” migration of PM v7.21 and may be upgraded to PM v7.31 in future. At this moment, just checking the technical feasibility /fitment analysis
Required a quick clarification – Does existing functionalities will work as expected, if the clone of the PM v7.21 in the Pega v7.2.1 is migrated to Pega v7.3.1 (not considering database as SQL Server)? Any constraint or impact to functionalities if this approach is considered.
Built-on application stack remain same for Pega v7.2.1 and Pega v7.3.1 respectively.
Ideally expecting all the existing functionalities will be working expected after migration with this approach. Any suggestions?
Thanks in advance.
Regards
SVAQuest
At risk of making an out of scope type statement, if you are just analyzing possibilities I would encourage to include Pega Marketing 7.4 also in your analysis. This has been released in April already and will this year be replaced by an even newer version, so even if you have a corporate policy requiring it to be the latest version -1 you, this will soon be Pega Marketing 7.4. Check the Pega Marketing and Customer Decision Hub sections for details.
As detailed by Manu, Pega Marketing will only work with certain versions of the platform. He stated that the version you referenced do not work together, so working through cloning options is not something that should be considered because at the end of the day, the product is not supported against that combination.