We are still in planning, but essentially doing the same thing. However, we are adding a new db to make it easier(?) .
As I understand it, two pureconnect environments connected to one DB are different Sites. This means that queue1 on system1 is a different DB entity than queue1 on system2. The same would be true with users.
To avoid jumping through reporting hoops, we plan to restore the existing DB to a new DB and use that for the upgrade. This should maintain the integrity of the entities and site number.
The $0.02 of our plan is:
- Restore existing DB to new DB
- Install Pureconnect (use existing DB during install process, using the new one)
- Use migrator to get appropriate configs (users, workgroups, attendant, etc.)
- Perform all testing
- On cutover night, restore existing DB. Then use setup assistant to upgrade the DB.
I know it's not really a report of success, but hopefully it gives you some help in planning.
------------------------------
Tim Cannon
Elevate Credit Services, LLC
------------------------------
Original Message:
Sent: 01-29-2019 13:02
From: Shane Jenkins
Subject: Merging SQL Databases
That's great to know and is interesting. Will have to think about that and we'd probably have to upgrade the db schema of the current prod database, as the newer IC version 2018 R5 would want an upgraded version. Wonder if the older 2017 R2 could continue writing to an upgraded db?
We are not planning to replace the actual DB servers. We just need to upgrade/replace our telephony servers w Windows 2016 and move off of older hardware running Windows 2008 R2.
As you say careful testing would need to be done. We do have a lab environment and have both versions of IC in our lab so we can potentially do some testing.
We're hopeful that some customers have been through this before and interested to learn what they learned/did.
Thanks much for the reply!
------------------------------
Shane Jenkins
SAIC
Original Message:
Sent: 01-29-2019 12:53
From: Paul Simpson
Subject: Merging SQL Databases
I'm not sure if this will help, but you are aware that multiple IC servers can report to the same database? If you are not replacing the actual DB servers, this may be an option. Obviously, careful testing will be required....
------------------------------
Paul Simpson
Senior Technical Instructor
Original Message:
Sent: 01-29-2019 12:30
From: Shane Jenkins
Subject: Merging SQL Databases
Hello all,
We are operating a 2017R2 environment supporting multiple customers and are in process of standing up 2018R5 both on premise with new servers/hardware. In doing this we will be incrementally migrating customers from the old 2017R2 servers to the new 2018R5 servers.
Question is, has anyone successfully merged data between two different SQL databases given this type of scenario? We are a 24x7x365 operation and cannot afford to take any hard downtime.
We ran the then provided migration utility to migrate our SQL data when we moved from 3.0 to the 4.0 platform. We ran it multiple times successfully. We are hoping to do something similar this time around but so far haven't found a solid answer.
Hoping someone has attempted this before with positive results. Our goal is to migrate all historical data and if at all possible do it incrementally vs. all at once. (avoiding hard down time as well) We have an open ticket w support on this as well.
Thanks,
Shane
#Reporting/Analytics