This includes authentication of Active Directory principals federated with Azure Active Directory.
Affinity trace windows#
SQL Database doesn't support Windows authentication, but does support Azure Active Directory authentication.
As such, if your database to be migrated is using any of the following features, re-engineer your application to eliminate these T-SQL features and statements. In addition to T-SQL statements related to the unsupported features described in Azure SQL Database feature comparison, the following statements and groups of statements aren't supported. T-SQL syntax not supported in Azure SQL Database For more information, see CREATE LOGIN and ALTER LOGIN and Manage logins and users. To make your database more portable, SQL Database encourages using contained database users instead of logins whenever possible. CREATE LOGIN and ALTER LOGIN statements are supported, but do not offer all options available in SQL Server.The CREATE TABLE and ALTER TABLE statements have FILETABLE and FILESTREAM options that can't be used on SQL Database because these features aren't supported.CREATE DATABASE for Azure SQL Database also has service objective and elastic pool options that apply only to SQL Database.
Affinity trace code#
This may not matter if you create databases in SQL Database before you migrate, but if you're migrating T-SQL code that creates databases you should compare CREATE DATABASE (Azure SQL Database) with the SQL Server syntax at CREATE DATABASE (SQL Server T-SQL) to make sure all the options you use are supported. The statements include file placement, FILESTREAM, and service broker options that only apply to SQL Server. In SQL Server, CREATE DATABASE and ALTER DATABASE statements have over three dozen options.The core DDL statements are available, but DDL statement extensions related to unsupported features, such as file placement on disk, are not supported. T-SQL syntax statements with partial differences This page supplements that article, and focuses on T-SQL statements. T-SQL statements related to availability groups are not supported by SQL Database, and the dynamic management views related to Always On Availability Groups are also not supported.įor a list of the features that are supported and unsupported by SQL Database, see Azure SQL Database feature comparison. When such capabilities are required, an appropriate alternative is often available in some other way from SQL Database or from another Azure feature or service.įor example, high availability is built into Azure SQL Database. T-SQL statements and options aren't available if they configure instance-level options, operating system components, or specify file system configuration. As such, most instance-level features are not supported in SQL Database. In addition, there are some features and syntax that isn't supported at all because Azure SQL Database is designed to isolate features from dependencies on the system databases and the operating system. There are, however, a few T-SQL differences in DDL (data definition language) and DML (data manipulation language) elements resulting in T-SQL statements and queries that are only partially supported (which we discuss later in this article). For example, the core SQL components such as data types, operators, string, arithmetic, logical, and cursor functions work identically in SQL Server and SQL Database. Most T-SQL features that applications use are fully supported in both Microsoft SQL Server and Azure SQL Database. To detect incompatibilities and migrate databases to Azure SQL Database, use Data Migration Assistant (DMA). This article provides guidance to assist you in both performing this re-engineering and understanding the underlying reasons why the re-engineering is necessary. When migrating your database from SQL Server to Azure SQL Database, you may discover that your SQL Server databases require some re-engineering before they can be migrated.
0 kommentar(er)
