SQL Server Database Migration to Azure SQL Database — Move SQL Data to Azure

IT Partner’s SQL Server Database Migration to Azure SQL Database service migrates SQL Server databases to Azure SQL Database so the databases are available from Azure without data loss. The service includes migration execution, relevant compatibility assessment and fixes for the downtime-based method, transactional replication configuration for the replication-based method, application connection string changes for Method 2, and a project closeout report.

This service is specifically for migrating SQL Server databases to Azure SQL Database. It does not cover migration of a SQL Server database to SQL Server running in an Azure virtual machine; IT Partner has a separate service for that scenario.

The stated duration for this service is 1 week. The plan may vary depending on your needs, so any schedule details for a specific database environment should be confirmed with IT Partner during scoping or kickoff.

The service is priced at $150 per hour. The service SKU is ITPWW320MIGOT, and the final budget is documented in the project closeout report.

The listed service manager for IT Partner’s SQL Server Database Migration to Azure SQL Database service is Mike Mackey. You should confirm project-specific contacts and escalation paths with IT Partner at the start of the engagement.

You must have an Azure subscription before IT Partner can perform this migration to Azure SQL Database. You also need to provide required access to systems and services so IT Partner can complete the work.

The service includes two migration approaches: Method 1, a simpler migration with downtime, and Method 2, a more complex migration using SQL Server transactional replication. The source service content does not specify who chooses the method or exact selection criteria, so the right approach should be confirmed with IT Partner based on your downtime tolerance and technical requirements.

For Method 1, IT Partner assesses database compatibility using the latest version of Data Migration Assistant, prepares any required Transact-SQL fix scripts, makes a transactionally consistent copy of the source database, applies fixes to the copy, exports it to a local .BACPAC file, and imports it as a new Azure SQL database. This method is simpler, but it can require substantial downtime because the source database must stop changing or changes must be manually applied after migration.

For Method 2, IT Partner configures Azure SQL Database as a subscriber to the SQL Server database being migrated and uses SQL Server transactional replication so changes to data or schema show up in Azure SQL Database. This method is more complex, but it substantially eliminates downtime during the migration compared with the downtime-based method.

Downtime depends on the migration method used. Method 1 requires some possibly substantial downtime, while Method 2 uses transactional replication and substantially eliminates downtime during the migration; the specific business impact should be confirmed with IT Partner for your environment.

The service objective is to make SQL databases available from Azure without data loss. For the downtime-based method, IT Partner makes a transactionally consistent copy and prevents further changes to the source database or requires manual application of later changes; for the replication method, transactional replication is used so changes to data or schema appear in Azure SQL Database.

Yes, for Method 1 IT Partner assesses database compatibility using the latest version of Microsoft Data Migration Assistant. If fixes are needed for that method, IT Partner prepares Transact-SQL scripts and deploys them to the database copy before import into Azure SQL Database.

Yes, for Method 2 the service includes changing the connection strings of your applications to point to the Azure SQL Database as part of the database migration. If you need connection string changes under a different migration approach or have complex application dependencies, confirm the specific scope with IT Partner.

IT Partner is responsible for the migration tasks defined by the selected method, such as compatibility assessment, Transact-SQL fix preparation, creation of a transactionally consistent database copy, .BACPAC export and import, transactional replication setup, and application connection string changes where included. IT Partner also verifies and fixes issues if any and provides a project closeout report.

The client must provide a dedicated point of contact, coordinate outside vendor resources and schedules, configure networking equipment such as load balancers, routers, firewalls, and switches, and provide required remote or physical access to facilities, systems, servers, and services. The client is also responsible for internal and external DNS changes as required.

The stated implementation plan includes a kickoff meeting, defining backup points and policy, starting deployment, finalizing deployment, and verifying and fixing issues if any. The plan may vary depending on your needs, so detailed project sequencing should be confirmed with IT Partner.

Deliverables include the migrated SQL databases in Azure SQL Database and a project closeout report showing final project status, evidence of meeting acceptance criteria, outstanding issues, and final budget. Depending on the migration method, the work may also include DMA assessment, Transact-SQL fix preparation and deployment, .BACPAC export/import activities, transactional replication configuration, and application connection string changes.

The included documentation is the project closeout report. More extensive documentation can be provided for an additional fee, but the source service description does not define the exact contents of that optional documentation, so you should confirm documentation requirements with IT Partner before the project starts.

After migration, IT Partner finalizes deployment, verifies and fixes issues if any, and provides a project closeout report. The report indicates final project status, evidence of meeting acceptance criteria, outstanding issues, and the final budget.

The stated success criterion is that SQL databases are available from Azure without data loss. Any environment-specific validation steps, application testing expectations, or acceptance procedures should be confirmed with IT Partner during the engagement.