A long-time client recently asked SSP Innovations to assist on a Network Migration project.

This client currently runs its IT systems within a DMZ network that is distinctly separated from the city network. However, the client desires to move all aspects of its IT systems to the city network to allow it to utilize the significant infrastructure and support resources already in place at the city.

In addition to moving the network infrastructure, this client wants to move its database application from Oracle to SQL Server as there are significantly more support resources available for SQL Server within the city’s IT department.

The client is also interested in techniques that could be used to increase efficiency when deploying software and data changes to the Production environment – and minimizing downtime during this process.

Because this is such a significant move, SSP completed an assessment and design phase (known as the Network Migration Assessment) in January. This was done in advance of the actual migration, and it provided the client with a concrete plan for the move.

The first step in the assessment was an onsite workshop with client staff to capture both their architecture requirements and their application and integration requirements.

The original strategy was to run these workshops in parallel. SSP’s Chief Technology Officer, Adam Tonkin, planned to lead the Application and Integration workshops (which were primarily focused on the shift from Oracle to SQL Server) while our DBA, Jeff Buturff, planned to lead the Architecture workshops (which were primarily focused on the proposed architecture for the move) at the same time. However, many of the topics overlapped so Jeff and Adam decided to run most of the meetings concurrently.

Once all the requirements were gathered, Adam and Jeff returned home to begin the documentation portion of the assessment. The first document detailed specs for the three new GIS and OMS environments: Production (where all the daily operations will occur, and all active integrations will perform data imports/exports/updates), QA (which will mimic Production), and Test.

The second document was focused on the migration: the migration of GIS and OMS databases from Oracle to SQL Server; the migration of GIS and OMS related software, code, and scripts; and the migration of GIS and OMS related maps and map services. This document also included a section of opportunities for efficiency gain as the migration takes place.

All the pieces are in place. The next step is to take the requirements included in the documents and begin to build out a Scope of Work and Project Schedule for the actual migration. Stay tuned…