You should probably ask Cisco to help you through this they can likely provide you with an updated document and jar file
- You will need to update your master.props settings.
- You will need potentially need a new jar
- Perform on a maintenance weekend with a maximum amount of recovery time
I have a Cisco doc and Zip files from 2010 when we did this but it is likely a different JAR that you would want to apply now.
What I would think are the Sequence of events (disclaimer Cisco would be best source of sequence, order, etc)
- set system queue to zero
- close all client sessions
- stop master services
- kill all connections to Admiral database
- backup admiral database
- set database offline and rename
- Restore admiral database backup to new target SQL server 2008 instances
- Creare a backup of master.props
- Apply Jar to update master / SQL scripts (if supplied by Cisco)
- Update master.props with new settings
- JdbcURL=jdbc:sqlserver://:;selectMethod=cursor;databaseName=Admiral (or Admiral DB name)
- There could be other setting that may also need to chance
- Start Tidal Master make sure it is running
- Connect Client
- Verify Connections
- Turn on System Queue slowly ramp up from a few to your standard level
