The Data Migration Assistant helps facilitate SQL Server migration assessments by allowing users to set the source and target server types, select assessment report types such as Compatibility Issues or New Features' Recommendation, and assess databases by connecting to SQL Server instances with provided connection properties . Users can add sources, select databases for assessment, and optionally include extended events trace files to capture workloads . The assessment results can be reviewed for compatibility issues and feature recommendations, and users can export these to a JSON or CSV file .

When planning a SQL Server upgrade to an on-premises modern server or an Azure VM, considerations include choosing the appropriate assessment report types: Compatibility Issues and New Features' Recommendations . Compatibility Issues highlight potential problems related to new server version compatibility, helping to prevent migration failures due to unsupported features . New Features' Recommendations provide insights into leveraging new capabilities that could improve performance, security, or storage efficiency at the target destination . Tailoring these assessments to the specific migration target will ensure that both breaking changes and opportunities for enhancement are thoroughly evaluated, thereby smoothing the upgrade process .

When utilizing SQL Server Backup to URL, page blobs support a maximum backup size of 1 TB, while block blobs are limited to 200 GB, unless striping is used, which allows for larger sizes . Block blobs require a Shared Access Signature (SAS) for multiple blob operations, whereas page blobs do not have this requirement. These differences imply that block blobs offer less straightforward usability due to required striping and SAS tokens, but they offer more flexibility in terms of managing larger data sets by breaking them into smaller parts for backup .

The Azure Migrate hub aids in extending SQL Server migration assessments by providing a centralized platform where users can upload results, consolidate data, and assess the readiness of entire data estates for Azure migration . Benefits over standalone assessments include comprehensive insight into estate-wide migration readiness, the ability to track migrations across multiple servers and databases simultaneously, and access to aggregated results that highlight common themes and issues . These capabilities enable more strategic planning and resource allocation, improving the efficiency and effectiveness of large-scale migrations .

Compatibility issues detected during migration to Azure SQL Database include partially supported or unsupported features such as breaking changes, behavior changes, and deprecated features . The assessment provides recommendations for resolving these issues, which might involve adapting or replacing unsupported features with available Azure alternatives and implementing mitigation strategies to address detected incompatibilities . Feature parity issues, including missing features in Azure SQL Database, might also appear, and similar recommendations will be provided .

To capture application workload using an extended event session for assessment, first, create an extended event session that captures relevant SQL Server events, such as sql_batch_completed, while attaching action items like sql_text and client app name . Designate an asynchronous file target for storing event data, and configure the session with suitable properties like max memory and event retention mode . Start the session, let it run during peak workload times, then query the captured events for analysis. Finally, stop the session to finalize data collection .

Saving assessment results as JSON or CSV files in the Data Migration Assistant provides advantages such as readability and wide compatibility with data processing tools . JSON files are useful for detailed data representation compatible with web applications, allowing for easy parsing and integration. CSV files are supported by spreadsheet applications like Microsoft Excel, facilitating accessibility for users to manually review and manipulate data. These formats also support automation in further processing and reporting, making them flexible and efficient for technical and business users alike .

Compatibility issues in the Data Migration Assistant relate to breaking changes, behavior changes, and deprecated features that could hinder migration . These issues must be addressed to ensure migration success. Feature recommendations suggest enhancements that offer new functionality or improvements in Performance, Storage, and Security, advising on features such as In-Memory OLTP, Columnstore, and Always Encrypted that can be exploited post-migration to enhance system capabilities . Each category serves different goals: one ensures compatibility while the other illustrates opportunities for modernization .

When using SQL Server Backup to multiple blobs, a key challenge involves managing the Shared Access Signature (SAS) token required instead of the storage account key, which adds complexity to authorization procedures . The solution involves carefully issuing SAS tokens with appropriate permissions and ensuring all backup operations are correctly authenticated with strings that do not expire during operations. It requires careful setup and management to avoid permissions errors and to support data integrity and security .

The setup for SQL Server Backup to URL using Azure Storage requires a Microsoft Azure account, an Azure storage account, MS SQL Server 2016 or 2017, SQL Server Agent, SSMS 17.X, and an Internet connection on the DB Server . Limiting factors include no support for premium storage, backup size limits of 1 TB for page blobs and 200 GB for block blobs unless striping is used, and a maximum backup device name length of 259 characters . Furthermore, appending to existing backup blobs is not supported; backups must be overwritten using the WITH FORMAT option unless using file-snapshot backups .