I posted this as a question to IFS via the Customer Engagement Center, but was told it was not “Unfortunately the raised case does not fall within the support scope as this is not a product fault . . . ”, so I would like to post it here in case any of the community has any thoughts or opinion on the matter.
During the course of our training, testing and deployment of TouchApps in our non-production environments, we have received conflicting opinions regarding the best practices of database configuration for TouchApps.
1.) Originally, when we worked with IFS, the configuration was to create a separate database dedicated to TouchApps
2.) Later, it was conveyed to us that IFS’s standard configuration for TouchApps was to extend the schema of the IFS database
As we approach going live with TouchApps in production, I would like to discuss this topic with someone very well versed in the pros and cons of these two configurations, specifically:
What impact do both of these configs have on the data "refresh" process (copying current PROD database down to test/dev instances?
Does every "non-prod" TouchApps server need a dedicated database if we do not extend the schema of the IFS database?
What are the performance issues associated with each of these configurations?
