cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

What all things should be taken into account when database under CAS/EP/CSS/RumConsole database is to be upgraded/migrated to a newer version of mssql?

andrew_n_matthe
Inactive

CAS/EP/CSS/RumCOnsole database migration from mssql2008 to mssql2012

What all things should be taken into account when database under CAS/EP/CSS/RumConsole is to be upgraded/migrated to a newer version of mssql?

Is this supported and possible to do without that our system fails after the migration? Is there something db-version dependent issues here?

What is Dynatrace's recommendation to this kind of change?

I would still like to have answer if some actions are needed to do from CAS/EP/CSS/Console side? Are there some updating scripts to be run that perhaps make something in those databases? Or is it really just that CAS and other DT products do not care at all if db version suddenly changes to newer one.

To be more clear, this is an running production env with existing database sql2008, and target is to stop the DT services, migrate the database by db specialist (they know what they do) to sql2012, and then start the same DT services as before against the new migrated database. Is there any actions we should do before we start DT services against the new version db? Without that we loose any data, the old data should be accessible.

1 REPLY 1

ulf_thorn222
Inactive

Thee are couple of ways you could approach this.

1: We do have a migration "department" Guidelines for migration to DCRUM 12.2.2 RELEASE but that focusses on the actual DC RUM migration but pop a question there.

2: Use our services guys - They shold be able (given a little feedback from you) to properly assess the work and give you a quote.

Me? I'm running both 2008 and 2012 but have never moved any data across (smile)