Hello,
Is there a way to retain the following during an upgrade or prior to go-live?
What are the best practices to follow during an upgrade or go-live process?
Which information can be retained, and which ones need to be re-deployed?
Best answer by subashfestus
Hi
Are there any tabular model configurations and data source configurations? If yes you have to export the configured objects before the DB replacement and then import again.
Data load/Process definitions will have to be recreated.
Environment setup needs to run again.
I’m not sure whether there is a way to export scheduled jobs. These tabular related scheduled jobs has to be treated as any other scheduled job.
Since the tabular model is already there in the Analysis Service there is no need to deploy them again as long as the SQL server is the same.
Best regards,
Subash
Hi
The tabular model is deployed to the Analysis Service and during an upgrade nothing will happen to the deployed tabular model there.
The tabular model metadata, dataload/process definitions, entity criteria are data stored in the database and those should not affect during the upgrade process.
The scheduled jobs related to Analysis Models functionality is similar to any other scheduled job in IFS. Those will also be treated same during the upgrade.
Best regards,
Subash
Hi
Thank you for the clarification!
One of our customers has a production environment setup for tabular models. However they are planning to replace the database with their IEE database during the go live. What will happen to the already deployed tabular models, environment setup and scheduled jobs in IFS? Should they be re-deployed/recreated since its a new database? Is there a way to retain those when deploying the new database?
Hi
Are there any tabular model configurations and data source configurations? If yes you have to export the configured objects before the DB replacement and then import again.
Data load/Process definitions will have to be recreated.
Environment setup needs to run again.
I’m not sure whether there is a way to export scheduled jobs. These tabular related scheduled jobs has to be treated as any other scheduled job.
Since the tabular model is already there in the Analysis Service there is no need to deploy them again as long as the SQL server is the same.
Best regards,
Subash
Hi
When you run the “Setup Tabular Model” assistant for a particular model, during the “Deploy Tables and views” step all the tables and views related to that tabular model will be dropped and recreated. When going live I would recommend doing this to get everything from a fresh state.
Also even without running that if you just want to load fresh data you have to use the “Full” load mode in the “data load definition”. “Full” data load mode will always TRUNCATE the table before loading data. Anyway for all dimensions always it will be a “Full” load. Only few facts support incremental loading.
After the data load you have to do a “Full” model process to get the new data.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
