SQL Server Upgrades, Always On and Azure SQL MI: How These Projects Actually Run

SQL Server Migration, Upgrades & Cloud Modernisation: 10 Common Business Scenarios

Modernise your SQL Server environment, reduce operational risks, improve database performance and build a more resilient IT infrastructure with Onsys Technologies.

For many organisations, Microsoft SQL Server is the foundation of business-critical applications, ERP systems, financial platforms, customer databases and operational reporting.

But as infrastructure ages, applications grow and cloud adoption accelerates, organisations face an important question:

Is your current SQL Server environment still the right platform for your business?

You might be running an unsupported SQL Server version, planning a migration to Microsoft Azure or Amazon Web Services (AWS), struggling with database performance, or looking to improve high availability and disaster recovery.

Whatever the challenge, SQL Server migration and modernisation projects require more than moving databases from one server to another.

A successful project must consider application compatibility, security, licensing, infrastructure costs, availability, performance and business continuity.

At Onsys Technologies, we help organisations across Australia and the Pacific plan, migrate, upgrade, optimise and protect their Microsoft SQL Server environments.

In this article, we explore ten common SQL Server projects, their business drivers, technical challenges and the benefits of getting them right.

1. SQL Server Version Upgrades – Move Away from Legacy and Unsupported Platforms

Is your business still relying on an outdated SQL Server version?

Many organisations continue operating older SQL Server versions because their databases are stable and business applications still work.

However, stability today does not eliminate tomorrow's risks.

SQL Server 2016 reached the end of extended support in July 2026. Earlier versions, including SQL Server 2012 and 2014, are also outside their normal support lifecycles.

Unsupported systems can create serious challenges:

• Increased exposure to unpatched security vulnerabilities

• Compliance and audit concerns

• Reduced compatibility with modern applications

• Limited support from software vendors

• Difficulties implementing modern security and availability capabilities

• Growing technical debt and maintenance costs

The modernisation opportunity

Upgrading to a supported version such as SQL Server 2022 or SQL Server 2025 can improve your long-term support position while opening opportunities for security, performance and operational improvements.

However, not every application can immediately move to the latest version. Vendor certification, deprecated features and compatibility requirements must be assessed first.

How Onsys helps

Our SQL Server upgrade services include:

• SQL Server environment and dependency assessment

• Application and database compatibility analysis

• SQL Server version and edition recommendations

• Side-by-side or in-place upgrade planning

• Migration of databases, logins, SQL Agent jobs and linked servers

• Pre-upgrade and post-upgrade performance benchmarking

• Backup validation, migration rehearsal and rollback planning

• Post-upgrade testing, optimisation and documentation

Business outcome: A supported, more secure SQL Server environment with a controlled transition and reduced operational risk.

2. On-Premises SQL Server to Microsoft Azure Migration

Is maintaining physical database infrastructure becoming expensive?

Many businesses are moving away from traditional data centres to reduce hardware dependencies, improve scalability and simplify infrastructure management.

Migrating SQL Server from on-premises servers to Microsoft Azure is a common step in cloud transformation.

Typical migration drivers include:

• Expiring server hardware and infrastructure warranties

• Data centre contract renewals

• Disaster recovery and business continuity improvements

• Increasing infrastructure maintenance costs

• Cloud-first IT strategies

• The need to scale workloads without purchasing new servers

Which Azure SQL platform should you choose?

There is no single Azure destination suitable for every SQL Server workload.

SQL Server on Azure Virtual Machines

Suitable for organisations that need operating system access, instance-level control or compatibility with existing SQL Server applications.

Azure SQL Managed Instance

A strong option for organisations looking to reduce SQL Server infrastructure administration while retaining many familiar instance-level capabilities.

Azure SQL Database

Often suitable for application modernisation, cloud-native solutions and individual databases that do not depend heavily on traditional SQL Server instance features.

How Onsys helps

• Assess existing SQL Server applications and dependencies

• Recommend the appropriate Azure SQL deployment model

• Design Azure networking, connectivity and security

• Assess licensing, storage, compute and ongoing costs

• Plan migration using supported Microsoft migration methods

• Minimise cutover disruption through rehearsal and synchronisation

• Configure backups, monitoring, resilience and access controls

• Validate application performance after migration

Business outcome: A cloud-ready SQL Server environment aligned with operational requirements, performance expectations and long-term costs.

3. On-Premises SQL Server to AWS Migration

Moving SQL Server to AWS? Choose the right migration strategy before moving your data.

AWS is another major cloud destination for organisations modernising Microsoft SQL Server environments.

Businesses may choose AWS to align with their broader cloud strategy, consolidate workloads, support global operations or move away from traditional data centres.

Two common migration approaches are available.

Option A: SQL Server on Amazon EC2

Amazon EC2 allows organisations to host SQL Server on Windows-based virtual machines with substantial control over the operating system, database configuration and supporting applications.

This approach can be appropriate when:

• Applications require full SQL Server instance capabilities

• Custom SQL Server configurations are necessary

• Operating system or file system access is required

• Existing high availability architectures must be retained or redesigned

• Applications depend on capabilities unsupported by managed database services

Option B: Amazon RDS for SQL Server

Amazon RDS for SQL Server provides a managed database service that handles many infrastructure administration activities, including automated backups and maintenance capabilities.

It can suit businesses seeking to reduce routine database infrastructure management.

However, RDS does not provide all the capabilities available in self-managed SQL Server installations. Certain SQL Server features, administrative permissions, integration services and high availability configurations have limitations.

An assessment of existing applications, SQL Agent jobs, linked servers, SSIS packages, database integrations and security requirements is essential before choosing RDS.

How Onsys helps

• SQL Server migration readiness assessment

• Amazon EC2 versus Amazon RDS suitability analysis

• AWS infrastructure and database architecture planning

• Database and application dependency assessment

• Migration strategy and cutover planning

• Backup, recovery and high availability configuration

• Database performance testing and optimisation

• Security hardening and post-migration validation

• Infrastructure and licensing cost assessment

Business outcome: A SQL Server environment on AWS designed for business continuity, manageable operating costs and application compatibility.

4. SQL Server Always On Availability Groups – Improve Business Continuity

What happens if your production SQL Server fails during business hours?

For businesses that rely on SQL Server to process transactions, support customers or run operational systems, database downtime can mean lost revenue, interrupted services and reputational damage.

SQL Server Always On Availability Groups can improve database availability and support disaster recovery strategies.

Depending on the architecture, availability groups can provide:

• Database redundancy across multiple servers

• Automatic or planned failover

• Reduced service interruption during supported failure scenarios

• Secondary replicas for disaster recovery

• Read-only workload offloading with supported configurations

• More flexible maintenance options

High availability requires more than a configured cluster

A successful Always On implementation depends on the entire architecture, including Windows Server Failover Clustering, network connectivity, quorum design, SQL Server editions and application failover behaviour.

SQL Server Standard Edition supports Basic Availability Groups with significant limitations compared with Enterprise Edition.

Availability Groups also do not automatically synchronise every instance-level component, including all SQL Agent jobs, logins and linked servers.

A failover that brings the database online but leaves applications unable to connect is not a successful recovery.

How Onsys helps

• High availability and disaster recovery requirements assessment

• Always On architecture and licensing recommendations

• Windows Server Failover Cluster configuration

• SQL Server Availability Group implementation

• Quorum, witness and failover design

• Secondary replica configuration

• Instance-level object synchronisation planning

• Application connectivity and failover testing

• Monitoring, documentation and operational handover

Business outcome: Greater database resilience, with a high availability solution that has been tested against defined failure scenarios.

5. SQL Server Disaster Recovery Migration and Modernisation

Backups are important. But can your organisation actually recover when disaster strikes?

A successful backup does not automatically mean your database can be restored within your business's required recovery window.

Organisations need to consider two important measures:

• Recovery Point Objective (RPO): How much data can the business afford to lose?

• Recovery Time Objective (RTO): How quickly must critical systems return to service?

Depending on business requirements, a disaster recovery solution may involve:

• SQL Server Always On Availability Groups

• SQL Server log shipping

• Failover Cluster Instances

• Cross-region cloud disaster recovery

• Backup and restore architectures

• Secondary database environments in another data centre

• Hybrid on-premises and cloud recovery options

Common business scenarios

A financial organisation may require recovery with very limited data loss.

A manufacturing business may need its operational database restored rapidly to prevent extended production downtime.

A regional organisation may need a disaster recovery environment in a separate geographical location.

Each requirement calls for a different architecture.

How Onsys helps

Onsys designs SQL Server disaster recovery solutions around business recovery targets, infrastructure constraints, licensing and budget.

Our engagements can include recovery architecture design, implementation, backup validation, recovery testing, failover runbooks and ongoing review.

Business outcome: A documented, tested recovery capability that supports business continuity when primary infrastructure fails.

6. SQL Server Data Centre Migration and Infrastructure Refresh

Planning to relocate your servers or replace ageing infrastructure?

Many organisations need to move SQL Server databases without changing their database platform.

Common scenarios include:

• Moving SQL Server between data centres

• Replacing ageing physical servers

• Migrating physical servers to virtual machines

• Moving SQL Server between VMware or Hyper-V environments

• Relocating databases to new storage infrastructure

• Moving workloads between hosting providers

Although these migrations may appear straightforward, they often involve hidden application dependencies.

These can include SQL Server logins, linked servers, SQL Agent jobs, SSIS packages, SSRS subscriptions, network configurations and application connection strings.

How Onsys helps

• Database inventory and dependency mapping

• Source and target infrastructure assessments

• Storage and SQL Server performance analysis

• Migration architecture and change planning

• Database synchronisation and cutover procedures

• Application connectivity validation

• Recovery and rollback preparation

• Post-migration testing and operational handover

Business outcome: A controlled infrastructure transition that reduces the risk of application disruption and unexpected database issues.

7. SQL Server Consolidation – Reduce Infrastructure Complexity and Costs

Are too many SQL Server instances increasing your operating costs?

As organisations grow, separate applications and departments frequently introduce new SQL Server instances.

Over time, this can create a fragmented database environment with:

• Underutilised servers

• Multiple SQL Server licensing commitments

• Inconsistent backup and maintenance configurations

• Increased administration overhead

• Different SQL Server patch levels

• Complex monitoring and security management

SQL Server consolidation can help organisations rationalise their database infrastructure.

Typical consolidation opportunities

• Consolidating multiple SQL Server instances onto fewer hosts

• Migrating departmental databases to shared infrastructure

• Standardising SQL Server versions

• Combining workloads with compatible performance and availability requirements

• Moving selected databases into managed cloud services

• Decommissioning unused or redundant SQL Server environments

However, consolidation must be carefully designed to avoid resource contention, incompatible configurations and increased failure impact.

How Onsys helps

Onsys evaluates database resource consumption, workload patterns, storage performance, licensing considerations and application dependencies before recommending a consolidation strategy.

Business outcome: Reduced operational complexity, improved infrastructure utilisation and potential licensing and administration savings.

8. SQL Server Performance Optimisation During Migration or Upgrade

Does your SQL Server experience slow queries, blocked transactions or unpredictable performance?

Migration and upgrade projects provide an opportunity to address long-standing SQL Server performance problems.

Moving a poorly optimised database to a new server or cloud platform does not automatically resolve inefficient queries, missing indexes or application design problems.

In some cases, performance can deteriorate if the target infrastructure is incorrectly sized or database configuration changes are not assessed.

Common SQL Server performance problems

• Slow-running SQL queries and stored procedures

• High CPU utilisation

• Memory pressure

• Excessive disk I/O and transaction log latency

• Blocking and deadlocks

• Missing, fragmented or inefficient indexes

• Poor query execution plans

• TempDB contention

• Outdated statistics

• Inappropriate SQL Server configuration settings

How Onsys helps

Our SQL Server performance optimisation approach can include:

• Query Store and execution plan analysis

• Wait statistics and workload assessment

• Index and statistics optimisation

• Stored procedure and SQL query tuning

• Storage and TempDB configuration review

• CPU, memory and MAXDOP configuration assessment

• Before-and-after performance benchmarking

• Post-upgrade regression analysis

Business outcome: Better SQL Server performance, more predictable application response times and improved infrastructure efficiency.

9. SQL Server Hybrid Cloud Migration – Keep Critical Systems Connected

Not ready to move every database to the cloud?

Many businesses operate applications across both on-premises infrastructure and cloud environments.

A hybrid SQL Server architecture can help organisations modernise gradually while retaining workloads that must remain on-premises.

Common requirements include:

• Keeping latency-sensitive databases near local applications

• Connecting on-premises SQL Server to Azure-hosted applications

• Using cloud infrastructure for selected disaster recovery workloads

• Migrating applications and databases in phases

• Maintaining hybrid environments during a lengthy modernisation program

• Meeting business, regulatory or data residency requirements

How Onsys helps

Onsys can assist with hybrid SQL Server architecture, secure connectivity, replication and synchronisation requirements, migration sequencing and disaster recovery planning.

The solution must account for network latency, supported replication technologies, application dependencies and the operational complexity of maintaining multiple environments.

Business outcome: A phased modernisation strategy that balances cloud adoption with business continuity and existing infrastructure investment.

10. SQL Server Managed Services and Post-Migration Support

Who will maintain and optimise SQL Server after the project is completed?

Migration is only one stage in the database lifecycle.

Once SQL Server is upgraded or moved to a new environment, organisations still need to maintain security, performance, recoverability and operational reliability.

Common ongoing requirements include:

• SQL Server health and performance monitoring

• Backup and restore validation

• Security and patch management

• Database capacity planning

• SQL Server Agent job monitoring

• Query and index optimisation

• High availability monitoring

• Database incident investigation

• Disaster recovery readiness reviews

• Technical support for application and infrastructure changes

How Onsys helps

Onsys provides SQL Server database administration and managed support services for organisations that need specialist expertise without expanding their internal DBA team.

Our services support on-premises, cloud and hybrid SQL Server environments, with project delivery and ongoing DBA support available as separate engagements.

Business outcome: Reliable database operations, access to specialist expertise and more time for internal IT teams to focus on strategic initiatives.

Which SQL Server Migration Strategy Is Right for Your Business?

Choosing the right modernisation approach depends on your applications, database architecture, operational requirements and long-term technology strategy.

The right choice is not always the newest platform or the most expensive high availability design.

It is the solution that meets your business requirements with acceptable risk, predictable operating costs and an architecture your team can support.

Our Approach: A Structured SQL Server Migration Methodology

At Onsys Technologies, we approach SQL Server upgrades and migrations as business-critical infrastructure changes.

Our delivery methodology focuses on reducing uncertainty before production cutover.

Phase 1: Discovery and Assessment

We review the existing SQL Server estate and identify the dependencies that can affect the project.

Activities may include:

• SQL Server version, edition and configuration inventory

• Database and application dependency assessment

• Performance and capacity analysis

• Security and backup review

• Compatibility and feature assessment

• Recovery requirements and downtime expectations

Phase 2: Architecture and Migration Planning

We recommend a target platform based on business and technical requirements.

The migration plan defines:

• Target SQL Server architecture

• Cloud or infrastructure configuration

• Licensing and operating cost considerations

• Security and network requirements

• Migration tooling and methodology

• Cutover window and rollback strategy

• Testing and acceptance criteria

Phase 3: Migration Preparation and Rehearsal

Before production migration, we prepare and validate the target environment.

Activities can include:

• Target server or cloud platform configuration

• SQL Server installation and configuration

• Database migration testing

• Application and integration testing

• Performance baseline comparison

• Migration rehearsal and rollback validation

Phase 4: Production Migration and Cutover

The production migration is executed using an agreed change plan.

Depending on the architecture, data synchronisation or log-based migration methods may help reduce downtime.

The cutover includes database validation, application connectivity checks and confirmation of critical business functions.

Phase 5: Optimisation, Documentation and Handover

After migration, we verify that the SQL Server environment meets agreed acceptance criteria.

We address identified performance issues, validate monitoring and backup operations, document the final architecture and provide an operational handover.

Ongoing SQL Server DBA support is available where required.

Why Organisations Choose Onsys Technologies

SQL Server migrations are not simply infrastructure projects. They affect the databases and applications that businesses rely on every day.

Choosing an experienced database partner helps organisations identify technical risks early and make better platform decisions.

What Onsys brings to your project:

• Specialist SQL Server expertise: Database migration, administration, optimisation, high availability and disaster recovery.

• Cloud and infrastructure knowledge: SQL Server solutions spanning on-premises infrastructure, Microsoft Azure and AWS.

• Business-focused architecture: Technology recommendations based on compatibility, cost, performance and operational needs.

• Structured project delivery: Defined deliverables, migration rehearsals, acceptance criteria and documented handover.

• Flexible engagement: Fixed-price delivery for clearly defined projects, with time-based consulting available for open-ended requirements.

• Australian database consultants: SQL Server project services delivered by Onsys consultants in Australia.

• Ongoing support options: Standalone project engagements or continued SQL Server DBA and managed support services.

Whether you are migrating a single production SQL Server or planning a wider database infrastructure modernisation program, Onsys can help you assess the available options and develop a practical implementation plan.

Frequently Asked Questions

Can SQL Server be migrated from on-premises to AWS?

Yes. SQL Server workloads can be migrated to Amazon EC2 or Amazon RDS for SQL Server, depending on application requirements and database features. EC2 offers greater administrative flexibility, while RDS provides managed database capabilities with certain restrictions.

Should we move SQL Server to Azure SQL Managed Instance or Azure Virtual Machines?

Azure SQL Managed Instance is often appropriate when organisations want to reduce infrastructure administration and retain many SQL Server instance-level features. Azure Virtual Machines may be preferable when applications require operating system access, specialised SQL Server features or greater configuration control.

A compatibility and cost assessment should guide the decision.

Can SQL Server migrations be completed with minimal downtime?

Yes, in many cases. Depending on the source and destination platforms, migration approaches such as log shipping, database replication, supported online migration services or continuous data synchronisation can reduce the production cutover window.

Actual downtime depends on the database size, transaction activity, migration technology, application architecture and validation requirements. Zero downtime should not be assumed.

Do we need to upgrade SQL Server before moving to the cloud?

Not necessarily. Some workloads can be migrated to cloud infrastructure on their existing supported SQL Server version. Others may benefit from upgrading before or after migration.

Combining a database engine upgrade with a platform migration can increase project complexity, so the sequence should be assessed carefully.

Does SQL Server Always On replace backups?

No. Always On improves availability but does not replace database backups. Data corruption, accidental deletion and certain application errors can propagate to secondary replicas. A separate backup and tested recovery strategy remains essential.

Can Onsys migrate SQL Server databases between cloud providers?

Onsys provides database and cloud migration consulting for Azure, AWS and on-premises environments. Cross-cloud migration feasibility depends on the source and destination platforms, application dependencies, licensing and supported migration methods.

How much does a SQL Server migration cost?

Migration cost depends on the number of databases, SQL Server versions, application dependencies, database size, downtime requirements, target infrastructure and testing complexity.

Onsys offers a free initial scoping consultation and fixed-price quotations for projects with clearly defined deliverables.

Can Onsys support SQL Server after migration?

Yes. Onsys provides SQL Server administration, performance optimisation, monitoring, troubleshooting and managed DBA services for businesses requiring continued specialist support.

Planning a SQL Server Upgrade or Migration? Talk to Onsys.

Your SQL Server environment should support business growth, not hold it back.

Whether you are upgrading an unsupported SQL Server version, migrating databases to AWS or Azure, implementing Always On Availability Groups, or modernising an ageing database estate, getting the architecture and migration strategy right is essential.

Onsys Technologies helps organisations across Australia and the Pacific reduce database migration risks and build reliable, secure and efficient SQL Server environments.

Let's discuss your next SQL Server project.

• Book a free 30-minute consultation to discuss your environment and migration requirements.

• Request a SQL Server migration assessment to identify suitable options, technical dependencies and project risks.

• Start with a free 20-point SQL Server health check to review your existing instance before planning your next upgrade.

Onsys Technologies — SQL Server Migration, Cloud Modernisation & Database Consulting Services across Australia and the Pacific.