My organization will soon be upgrading to a higher version of Ataccama, and I want to make sure the transition goes as smoothly as possible.
I'm reaching out to ask: What should I be documenting or looking out for before, during, and after the upgrade?
Some specific things I'm wondering:
Are there key areas (like DQ rules, workflows, configurations, etc.) that I should definitely back up or document?
What kind of testing should I plan for in UAT? Should I be validating things both before and after the upgrade?
Are there any common issues or changes I should be aware of that might affect how things work in the new version?
If anyone has experience with a recent version upgrade, I’d love to hear what worked well for you—or what you wish you had done differently!
Also, if there are any official resources or checklists from Ataccama that you found useful, feel free to share.
Thanks in advance!
Best answer by Rianna
Hello here are the notes I have related to upgrades 😊
We have a hybrid deployment where we manage the Ataccama Data Processing Engines in house, so maybe some of the below may not be relevant for you if you have a different deployment:
If Ataccama have recently released a new version, the team can get really busy with upgrade requests, so it is best to request an upgrade a few months in advance. However in quieter periods a time slot can be available a few weeks/1 month in advance.
The Ataccama Data Processing Engines and Ataccama ONE Web must be on the same versions for it to work. Because we have hybrid deployment we therefore have to co-ordinate the upgrade of the DPE(s) in house with the timing of the Ataccama ONE Web upgrade.
If you upgrade frequently (for example we upgrade once a year), normally Ataccama ONE Desktop is still compatible if your Ataccama Web is on a newer version than your Ataccama ONE Desktop. So normally we would upgrade the Ataccama ONE Web first.
We haven’t experienced any issues with “losing” implementation work after an upgrade. But we have had some minor issues like layout/view issues. So I recommend after an upgrade check all the views (catalog item overview, sources overview, etc.) to see if everything looks in order. Whenever we have had an issue, Ataccama have fixed it quickly.
Normally Ataccama need half a day to upgrade an environment so it will be unavailable for use in this period.
If you have any ONE Desktop plans that imports data from the Ataccama metadata model, also test these after the upgrade as we have experienced before name changes in the metadata model in the upgrade which then broke our ONE desktop plans and we had to correct the plan to the new metadata model names.
We have multiple environments (DEV, TEST and PROD) so we would normally leave at least a 1 week gap in the planning with Ataccama to upgrade each environment so we have time to fix any issues experienced before upgrading the next environment.
Hello here are the notes I have related to upgrades 😊
We have a hybrid deployment where we manage the Ataccama Data Processing Engines in house, so maybe some of the below may not be relevant for you if you have a different deployment:
If Ataccama have recently released a new version, the team can get really busy with upgrade requests, so it is best to request an upgrade a few months in advance. However in quieter periods a time slot can be available a few weeks/1 month in advance.
The Ataccama Data Processing Engines and Ataccama ONE Web must be on the same versions for it to work. Because we have hybrid deployment we therefore have to co-ordinate the upgrade of the DPE(s) in house with the timing of the Ataccama ONE Web upgrade.
If you upgrade frequently (for example we upgrade once a year), normally Ataccama ONE Desktop is still compatible if your Ataccama Web is on a newer version than your Ataccama ONE Desktop. So normally we would upgrade the Ataccama ONE Web first.
We haven’t experienced any issues with “losing” implementation work after an upgrade. But we have had some minor issues like layout/view issues. So I recommend after an upgrade check all the views (catalog item overview, sources overview, etc.) to see if everything looks in order. Whenever we have had an issue, Ataccama have fixed it quickly.
Normally Ataccama need half a day to upgrade an environment so it will be unavailable for use in this period.
If you have any ONE Desktop plans that imports data from the Ataccama metadata model, also test these after the upgrade as we have experienced before name changes in the metadata model in the upgrade which then broke our ONE desktop plans and we had to correct the plan to the new metadata model names.
We have multiple environments (DEV, TEST and PROD) so we would normally leave at least a 1 week gap in the planning with Ataccama to upgrade each environment so we have time to fix any issues experienced before upgrading the next environment.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
