SQL Server EOS Modernization Services

Extended End

Jul. 9, 2019

Jul. 9, 2019

Jul. 12, 2022

Jul. 9, 2024

Jul. 14, 2026

Oct. 12, 2027

Jan. 8, 2030

Jan. 11, 2033

Heraflux offers two methods to help you modernize your enterprise SQL Servers – the Guided Package or White Glove Services.
Our Guided Package entails mentorship and a guide to your staff on the right approaches and methodologies to allow them to perform the upgrade to a newer SQL Server. Our White Glove Services works directly with your staff to assist in the migration efforts.

• Map out all dependencies on source server with Client so that all migration components are identified. This list could include SQL Server instance and database settings, dependencies such as linked servers, credentials and proxies, integration and reporting packages, database requirements and space estimates. This list could also include other required software outside of SQL Server.
• Review business continuity components such as server and database backups, high availability and/or disaster recovery architectures, or other factors for data recovery.
• Discuss the appropriate target service, such as on-premises SQL Server instances or cloud-based XaaS services.
• Guide in the deployment of new server(s) or cloud services, and verify that the construction meets or exceeds industry-standard baselines for performance and availability.
• Guide in the appropriate method(s) for migrating test copies of items such as databases, logins, and scheduled jobs, so that the target servers can be tested.
• Discuss the need to identify and validate sources of data integration or reporting, such as SSIS / Data Factory packages or SSRS / PowerBI reports.
• Guide on identifying external data sources, both inbound and outbound, that must be identified and documented for accomodation during the migration.
• Discuss the map out the appropriate migration method for the candidate servers, including methods for rolling the migration back if it goes awry.
• Guide and creation of the actual migration steps, technical details, and automation for the upcoming migration.

• Map out all dependencies on source server with Client so that all migration components are identified. This list could include SQL Server instance and database settings, dependencies such as linked servers, credentials and proxies, integration and reporting packages, database requirements and space estimates. This list could also include other required software outside of SQL Server.
• Review business continuity components such as server and database backups, high availability and/or disaster recovery architectures, or other factors for data recovery. Discuss SLAs and current practices, and discuss available SQL Server and infrastructure-related high availability and disaster recovery options to determine if a more advanced HA/DR architecture is required.
• Discuss the appropriate target service, such as on-premises SQL Server instances or cloud-based XaaS services.
• Perform a performance review of the source server to identify resource consumption patterns, and generate a “right-sized” server target recommendation that is used to budget SQL Server / service licensing on to save operational costs.
• Assist in the deployment of new server(s) or cloud services, and verify that the construction meets or exceeds industry-standard baselines for performance and availability.
• Assist in migrating test copies of items such as databases, logins, and scheduled jobs, so that the target servers can be tested.
• Validate any detected sources of data integration or reporting, such as SSIS / Data Factory packages or SSRS / PowerBI reports.
• Identify external data sources, both inbound and outbound, that must be identified and documented for accomodation during the migration. If appropriate, lead discussions on application-level adjustments required to continue to operate with target server architecture.
• Identify and map out the appropriate migration method for the candidate servers, including methods for rolling the migration back if it goes awry. Identify all possible data points of entry, source applications, connection mechanisms, and integration items that must be accommodated during the migration.
• Assist in the creation of the actual migration steps, technical details, and create and validate any automation for the upcoming migration.
• Guide application owners in the testing of any application functionality that can be replicated on the new target server for application-level functionality validation.
• Prior to the migration but after all app-level testing is completed, determine if a regular migration method, such as backup/copy/restore of the database and associated objects is sufficient, or if advanced migration preparations are needed, and implement such preparation items to facilitate reduced downtime during the actual migration.
• During the migration, work with Client to perform the SQL Server migration to the target services, and work with Client to confirm application functionality is intact.
• Support the target server the next business day after the migration to validate performance and functionality.
• One week after the migration, perform a baseline and health check on the target server to validate the platform, review for performance optimizations including indexing, changes in CPU consuming commands, and concurrency, and work with Client to perform remediations as necessary.

If you are interested in our SQL Server data modernization services, please do not hesitate to schedule a call to learn more about how we can help!