Following a DMSII upgrade, UW discovered that long replication times were negatively affecting data quality and productivity, which required changes in data replication configuration and set-up.
UW relies on its Unisys mainframe and DMSII database for key applications, such as financial systems and student information systems. An in-house developed DMSII extraction component was introduced in the mid-1990s to enable more effective operational data access by easily replicating large volumes of mainframe-based data to relational databases, such as SQL Server, Sybase, and Informix. Eliminating customized mainframe reporting, data extraction and file transfer routines saves times, improves the flexibility and quality of the data being made available, and reduces the burden on processing resources. The data is vital for budget setting and analysis, as well as course planning.
After many years of successful operation, when UW upgraded its DMSII system, it ran into unexpected problems. Elizabeth Runkle, Technology Manager for the university, explains the problems: “We were suddenly experiencing issues with replicating compact data sets on the relational database side. Records were dropped and we had a real integrity problem. We also noticed that replication was taking about seven hours after the upgrade. This was unacceptable for us and we suspected some rigorous data reorganization was needed.”
A test of the replication after adding the Micro Focus Databridge relational database client demonstrated a solution to the data replication integrity issue, and Runkle and the team embarked on a project to introduce Databridge across the board.