您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

Azure SQL 数据库功能Azure SQL Database Features

Azure SQL 数据库服务使用最新稳定版本的 SQL Server 共享公共基本代码。Azure SQL Database service shares a common code base with the latest stable version of SQL Server. 大多数标准 SQL 语言、查询处理和数据库管理功能在 SQL Server 和 Azure SQL 数据库中都是相同的。Most of the standard SQL language, query processing, and database management features are identical in SQL Server and Azure SQL Database. SQL Server 和所有类型的 Azure SQL 数据库中常见的功能如下:The features that are common in SQL Server and all flavors of Azure SQL Database are:

Azure SQL Database 管理数据库并保证其高可用性。Azure SQL Database manages your databases and guarantees their high-availability. 某些可能影响高可用性或无法在 PaaS world 中使用的功能在 Azure SQL 数据库中的功能有限。Some features that might affect high-availability or cannot be used in PaaS world have limited functionalities in Azure SQL Database. 此外,某些数据库功能取决于你创建的 Azure SQL 数据库的类型。In addition, some database features depend on the type of Azure SQL Database that you create. 下表中描述了这些功能。These features are described in the tables below. 使用 Azure SQL 数据库,可以作为托管实例、单一数据库或弹性池的一部分创建一个数据库。With Azure SQL Database, you can create a database as part of a managed instance, as a single database, or as part of an elastic pool. 如果需要更多有关差异的详细信息,可以在单个数据库和弹性池的单独页面或托管实例中找到它们。If you need more details about the differences, you can find them in the separate pages for Single database and Elastic pools or Managed Instance.

SQL 功能SQL features

下表列出了 SQL Server 的主要功能,并提供了托管实例或单一数据库和弹性池中是否部分或完全支持该功能的相关信息,并提供了指向有关此功能的详细信息的链接。The following table lists the major features of SQL Server and provides information about whether the feature is partially or fully supported in Managed Instance or Single Database and Elastic pools, with a link to more information about the feature.

SQL 功能SQL Feature 单一数据库和弹性池Single databases and elastic pools 托管实例和实例池Managed instances and instance pools
Always EncryptedAlways Encrypted 是 - 请参阅证书存储密钥保管库Yes - see Cert store and Key vault 是 - 请参阅证书存储密钥保管库Yes - see Cert store and Key vault
Always On 可用性组Always On Availability Groups 为每个数据库保证99.99-99.995% 的可用性99.99-99.995% availability is guaranteed for every database. 简要介绍如何使用 Azure SQL 数据库确保业务连续性中对灾难恢复进行了讨论Disaster recovery is discussed in Overview of business continuity with Azure SQL Database 99.99。可保证每个数据库的可用性,并且不能由用户进行管理99.99.% availability is guaranteed for every database and cannot be managed by user. 灾难恢复在AZURE SQL 数据库的业务连续性概述中进行了介绍。Disaster recovery is discussed in Overview of business continuity with Azure SQL Database. 使用自动故障转移组配置另一区域中的辅助 Always On 托管实例。Use Auto-failover groups to configure secondary Always On Managed Instance in another region. 不能将其他 SQL Server 实例和单一数据库用作托管实例的辅助数据库。Other SQL Server instances and Single databases cannot be used as secondaries for Managed Instance.
附加数据库Attach a database NoNo NoNo
审核Auditing Yes ,但有一些差异Yes, with some differences
Azure Active Directory (AAD)身份验证Azure Active Directory (AAD) authentication 可以。Yes. 仅限 AAD 用户。AAD users only. 可以。Yes. 包括服务器级别 AAD 登录名。Including server-level AAD logins.
备份命令BACKUP command 否,仅系统启动的自动备份 - 请参阅自动备份No, only system-initiated automatic backups - see Automated backups 是,用户启动的仅复制备份到 Azure Blob 存储(用户无法启动自动系统备份)-请参阅备份差异Yes, user initiated copy-only backups to Azure Blob Storage (automatic system backups cannot be initiated by user) - see Backup differences
内置函数Built-in functions 大多数 - 请参阅单个函数Most - see individual functions 是 - 请参阅存储过程、函数和触发器差异Yes - see Stored procedures, functions, triggers differences
BULK INSERT 语句BULK INSERT statement 可以,只需从 Azure Blob 存储作为源。Yes, but just from Azure Blob storage as a source. 是的,但只需从 Azure Blob 存储作为源-请参阅不同之处Yes, but just from Azure Blob Storage as a source - see differences.
证书和非对称密钥Certificates and asymmetric keys 是,无需访问文件系统 BACKUP 和 @no__t 操作。Yes, without access to file system for BACKUP and CREATE operations. 是,无需访问文件系统 BACKUPCREATE 操作-请参阅证书差异Yes, without access to file system for BACKUP and CREATE operations - see certificate differences.
变更数据捕获-CDCChange data capture - CDC NoNo Yes
排序规则 - 服务器/实例Collation - server/instance 不,默认逻辑服务器排序规则 SQL_Latin1_General_CP1_CI_AS 始终使用。No, default logical server collation SQL_Latin1_General_CP1_CI_AS is always used. 是,可以在创建实例时设置,稍后不能更新。Yes, can be set when the instance is created and cannot be updated later.
列存储索引Columnstore indexes 是-高级层,标准层-S3 及更高版本,常规用途层、业务关键和超大规模层Yes - Premium tier, Standard tier - S3 and above, General Purpose tier, Business Critical, and HyperScale tiers Yes
公共语言运行时-CLRCommon language runtime - CLR NoNo 是,但没有访问文件系统的 CREATE ASSEMBLY 语句-请参阅CLR 差异Yes, but without access to file system in CREATE ASSEMBLY statement - see CLR differences
凭据Credentials 是,但仅限数据库范围的凭据Yes, but only database scoped credentials. 是,但仅支持Azure Key VaultSHARED ACCESS SIGNATURE 查看详细信息Yes, but only Azure Key Vault and SHARED ACCESS SIGNATURE are supported see details
跨数据库/三部分名称查询Cross-database/three-part name queries 否 - 请参阅弹性查询No - see Elastic queries 是,外加弹性查询Yes, plus Elastic queries
跨数据库事务Cross-database transactions NoNo 是,在实例中。Yes, within the instance. 有关跨实例查询,请参阅链接服务器差异See Linked server differences for cross-instance queries.
数据库邮件-DbMailDatabase mail - DbMail NoNo Yes
数据库镜像Database mirroring NoNo No
数据库快照Database snapshots NoNo NoNo
DBCC 语句DBCC statements 大多数 - 请参阅单个语句Most - see individual statements 是 - 请参阅 DBCC 差异Yes - see DBCC differences
DDL 语句DDL statements 大多数 - 请参阅单个语句Most - see individual statements 是 - 请参阅 T-SQL 差异Yes - see T-SQL differences
DDL 触发器DDL triggers 仅数据库Database only Yes
分布式分区视图Distributed partition views NoNo Yes
分布式事务 - MS DTCDistributed transactions - MS DTC 否 - 请参阅弹性事务No - see Elastic transactions 否-请参阅链接服务器差异No - see Linked server differences. 尝试在迁移过程中将多个分布式 SQL Server 实例中的数据库合并到一个托管实例。Try to consolidate databases from several distributed SQL Server instances into one managed instance during migration.
DML 触发器DML triggers 大多数 - 请参阅单个语句Most - see individual statements Yes
DMVDMVs 大多数 - 请参阅单个 DMVMost - see individual DMVs 是 - 请参阅 T-SQL 差异Yes - see T-SQL differences
事件通知Event notifications 否 - 请参阅警报No - see Alerts NoNo
表达式Expressions Yes Yes
扩展事件(XEvent)Extended events (XEvent) 部分 - 请参阅 SQL 数据库中的扩展事件Some - see Extended events in SQL Database 是 - 请参阅扩展事件的差异Yes - see Extended events differences
扩展的存储过程Extended stored procedures NoNo NoNo
文件和文件组Files and file groups 仅限主文件组Primary file group only 可以。Yes. 文件路径是自动分配的,不能在 ALTER DATABASE ADD FILE语句中指定文件位置。File paths are automatically assigned and the file location cannot be specified in ALTER DATABASE ADD FILE statement.
文件流Filestream NoNo No
全文搜索(FT 数)Full-text search (FTS) 是,但不支持第三方断字符Yes, but third-party word breakers are not supported 是,但不支持第三方断字符Yes, but third-party word breakers are not supported
函数Functions 大多数 - 请参阅单个函数Most - see individual functions 是 - 请参阅存储过程、函数和触发器差异Yes - see Stored procedures, functions, triggers differences
内存中优化In-memory optimization 是-高级和业务关键层仅对非持久性内存中对象(如表类型)的支持有限Yes - Premium and Business Critical tiers only Limited support for non-persistent In-Memory objects such as table types 是 - 仅限业务关键层Yes - Business Critical tier only
语言元素Language elements 大多数 - 请参阅单个元素Most - see individual elements 是 - 请参阅 T-SQL 差异Yes - see T-SQL differences
链接服务器Linked servers 否 - 请参阅弹性查询No - see Elastic query 可以。Yes. 仅适用于没有分布式事务的SQL Server 和 SQL 数据库Only to SQL Server and SQL Database without distributed transactions.
从文件(CSV,Excel)读取的链接服务器Linked servers that read from files (CSV, Excel) 不。No. 使用BULK INSERTOPENROWSET作为 CSV 格式的替代方法。Use BULK INSERT or OPENROWSET as an alternative for CSV format. 不。No. 使用BULK INSERTOPENROWSET作为 CSV 格式的替代方法。Use BULK INSERT or OPENROWSET as an alternative for CSV format. 托管实例反馈项上跟踪此请求Track this requests on Managed Instance Feedback item
日志传送Log shipping 每个数据库均包含高可用性High availability is included with every database. 简要介绍如何使用 Azure SQL 数据库确保业务连续性中对灾难恢复进行了讨论Disaster recovery is discussed in Overview of business continuity with Azure SQL Database 作为 DMS 迁移过程的一部分内置内置。Natively built in as a part of DMS migration process. 不可用作高可用性解决方案,因为每个数据库都附带了其他高可用性方法,因此不建议使用日志传送作为 HA 替代方法。Not available as High availability solution, because other High availability methods are included with every database and it is not recommended to use Log-shipping as HA alternative. 灾难恢复在AZURE SQL 数据库的业务连续性概述中进行了介绍。Disaster recovery is discussed in Overview of business continuity with Azure SQL Database. 不能作为数据库之间的复制机制,使用业务关键层上的辅助副本、自动故障转移组事务复制作为替代项。Not available as a replication mechanism between databases - use secondary replicas on Business Critical tier, auto-failover groups, or transactional replication as the alternatives.
登录名和用户Logins and users 是的,但 @no__t 0 和 @no__t 登录语句不提供所有选项(无窗口和服务器级 Azure Active Directory 登录)。Yes, but CREATE and ALTER login statements do not offer all the options (no Windows and server-level Azure Active Directory logins). 不支持 EXECUTE AS LOGIN-改为改用 EXECUTE AS USEREXECUTE AS LOGIN is not supported - use EXECUTE AS USER instead. 是,但有一些差异Yes, with some differences. 不支持 Windows 登录名,并且应将其替换为 Azure Active Directory 登录名。Windows logins are not supported and they should be replaced with Azure Active Directory logins.
批量导入中的最小日志记录Minimal logging in bulk import 否,仅支持完整恢复模式。No, only Full Recovery model is supported. 否,仅支持完整恢复模式。No, only Full Recovery model is supported.
修改系统数据Modifying system data NoNo Yes
OLE 自动化OLE Automation NoNo NoNo
OPENDATASOURCEOPENDATASOURCE NoNo 是,仅适用于其他 Azure SQL 数据库和 SQL Server。Yes, only to other Azure SQL Databases and SQL Servers. 请参阅t-sql 差异See T-SQL differences
OPENQUERYOPENQUERY NoNo 是,仅适用于其他 Azure SQL 数据库和 SQL Server。Yes, only to other Azure SQL Databases and SQL Servers. 请参阅t-sql 差异See T-SQL differences
OPENROWSETOPENROWSET 是,仅用于从 Azure Blob 存储导入。Yes, only to import from Azure Blob storage. 是,仅适用于其他 Azure SQL 数据库和 SQL Server,并从 Azure Blob 存储中导入。Yes, only to other Azure SQL Databases and SQL Servers, and to import from Azure Blob storage. 请参阅t-sql 差异See T-SQL differences
运算符Operators 大多数 - 请参阅单个运算符Most - see individual operators 是 - 请参阅 T-SQL 差异Yes - see T-SQL differences
PolybasePolybase 不。No. 可以使用 OPENROWSET 函数查询放置在 Azure Blob 存储上的文件中的数据。You can query data in the files placed on Azure Blob Storage using OPENROWSET function. 不。No. 可以使用 OPENROWSET 函数查询放置在 Azure Blob 存储上的文件中的数据。You can query data in the files placed on Azure Blob Storage using OPENROWSET function.
查询通知Query Notifications NoNo Yes
R 服务R Services 是,处于公开预览状态Yes, in public preview NoNo
恢复模式Recovery models 仅支持保证高可用性的完全恢复。Only Full Recovery that guarantees high availability is supported. 简单和大容量日志恢复模式不可用。Simple and Bulk Logged recovery models are not available. 仅支持保证高可用性的完全恢复。Only Full Recovery that guarantees high availability is supported. 简单和大容量日志恢复模式不可用。Simple and Bulk Logged recovery models are not available.
资源调控器Resource governor NoNo Yes
RESTORE 语句RESTORE statements NoNo 是,对于放置在 Azure Blob 存储上的备份文件,具有必需的 FROM URL 选项。Yes, with mandatory FROM URL options for the backups files placed on Azure Blob Storage. 请参阅还原差异See Restore differences
从备份还原数据库Restore database from backup 仅从自动备份 - 请参阅 SQL 数据库恢复From automated backups only - see SQL Database recovery 从自动备份-请参阅SQL 数据库恢复和来自 Azure Blob 存储的完整备份-请参阅备份差异From automated backups - see SQL Database recovery and from full backups placed on Azure Blob Storage - see Backup differences
将数据库还原到 SQL ServerRestore database to SQL Server 不。No. 使用 BACPAC 或 BCP 而不是本机还原。Use BACPAC or BCP instead of native restore. 不能,因为托管实例中使用的 SQL Server 数据库引擎的版本高于在本地使用的任何 SQL Server RTM 版本。No, because SQL Server Database Engine used in Managed Instance has higher version than any RTM version of SQL Server used on-premises. 请改用 BACPAC、BCP 或事务复制。Use BACPAC, BCP, or Transactional replication instead.
语义搜索Semantic search NoNo NoNo
Service BrokerService Broker NoNo 是,但仅在实例内。Yes, but only within the instance. 如果使用远程 Service Broker 路由,请在迁移期间尝试将多个分布式 SQL Server 实例中的数据库合并为一个托管实例,并只使用本地路由。If you are using remote Service Broker routes, try to consolidate databases from several distributed SQL Server instances into one managed instance during migration and use only local routes. 请参阅Service Broker 差异See Service Broker differences
服务器配置设置Server configuration settings NoNo 是 - 请参阅 T-SQL 差异Yes - see T-SQL differences
SET 语句Set statements 大多数 - 请参阅单个语句Most - see individual statements 是 - 请参阅 T-SQL 差异Yes - see T-SQL differences
SQL Server 代理SQL Server Agent 否 - 请参阅弹性作业No - see Elastic jobs 是 - 请参阅 SQL Server 代理差异Yes - see SQL Server Agent differences
SQL Server 审核SQL Server Auditing 否 - 请参阅 SQL 数据库审核No - see SQL Database auditing 是 - 请参阅审核差异Yes - see Auditing differences
系统存储函数System stored functions 大多数 - 请参阅单个函数Most - see individual functions 是 - 请参阅存储过程、函数和触发器差异Yes - see Stored procedures, functions, triggers differences
系统存储过程System stored procedures 部分 - 请参阅单个存储过程Some - see individual stored procedures 是 - 请参阅存储过程、函数和触发器差异Yes - see Stored procedures, functions, triggers differences
系统表System tables 部分 - 请参阅单个表Some - see individual tables 是 - 请参阅 T-SQL 差异Yes - see T-SQL differences
系统目录视图System catalog views 部分 - 请参阅单个视图Some - see individual views 是 - 请参阅 T-SQL 差异Yes - see T-SQL differences
TempDBTempDB 可以。Yes. 每个数据库的32GB 大小(每个核心)。32GB size per core for every database. 可以。Yes. 整个 GP 层的每个 vCore 的24GB 大小,并受 BC 层上的实例大小限制24GB size per vCore for entire GP tier and limited by instance size on BC tier
临时表Temporary tables 本地和数据库范围的全局临时表Local and database-scoped global temporary tables 本地和实例范围的全局临时表Local and instance-scoped global temporary tables
时区选项Time zone choice NoNo 的,必须在创建托管实例时配置。Yes, and it must be configured when the Managed Instance is created.
跟踪标志Trace flags NoNo 是,但仅限有限的全局跟踪标志集。Yes, but only limited set of global trace flags. 请参阅DBCC 差异See DBCC differences
事务复制Transactional Replication 是,仅限事务复制和快照复制订阅服务器Yes, Transactional and snapshot replication subscriber only 是,在公共预览版中。Yes, in public preview. 请参阅此处的限制。See the constraints here.
透明数据加密 (TDE)Transparent data encryption (TDE) 是 - 仅限“常规用途”和“业务关键”服务层级Yes - General Purpose and Business Critical service tiers only Yes
Windows 身份验证Windows authentication NoNo NoNo
Windows Server 故障转移群集Windows Server Failover Clustering 不。No. 每个数据库都附带了提供高可用性的其他技术。Other techniques that provide high availability are included with every database. 简要介绍如何使用 Azure SQL 数据库确保业务连续性中对灾难恢复进行了讨论Disaster recovery is discussed in Overview of business continuity with Azure SQL Database 不。No. 每个数据库都附带了提供高可用性的其他技术。Other techniques that provide high availability are included with every database. 简要介绍如何使用 Azure SQL 数据库确保业务连续性中对灾难恢复进行了讨论Disaster recovery is discussed in Overview of business continuity with Azure SQL Database

平台功能Platform capabilities

Azure 平台提供了许多 PaaS 功能,这些功能添加为标准数据库功能的附加值。Azure platform provides a number of PaaS capabilities that are added as an additional value to the standard Database features. 有许多可用于 Azure SQL 数据库服务的外部服务。There is a number of external services that can be used with Azure SQL Database service.

平台功能Platform Feature 单一数据库和弹性池Single databases and elastic pools 托管实例和实例池Managed instances and instance pools
活动异地复制Active geo-replication 是-除超大规模以外的所有服务层Yes - all service tiers other than hyperscale 否,请参阅自动故障转移组作为替代方法No, see Auto-failover groups as an alternative
自动故障转移组Auto-failover groups 是-除超大规模以外的所有服务层Yes - all service tiers other than hyperscale 是,请参阅自动故障转移组Yes, see Auto-failover groups
自动缩放Auto-scale 是,但只能在无服务器模型中。Yes, but only in serverless model. 在非服务器模式下,服务层(vCore、存储或 DTU)的更改速度快且处于联机状态。In the non-serverless model, the change of service tier (change of vCore, storage, or DTU) is fast and online. 服务层更改需要最少或没有停机时间。The service tier change requires minimal or no downtime. 不需要,你需要选择 "保留计算和存储"。No, you need to choose reserved compute and storage. 服务层(vCore 或最大存储)的更改处于联机状态,需要最少或没有停机时间。The change of service tier (vCore or max storage) is online and requires minimal or no downtime.
自动备份Automatic backups 可以。Yes. 每7天、每隔12小时和每5-10 分钟执行一次完整备份。Full backups are taken every 7 days, differential 12 hours, and log backups every 5-10 min. 可以。Yes. 每7天、每隔12小时和每5-10 分钟执行一次完整备份。Full backups are taken every 7 days, differential 12 hours, and log backups every 5-10 min.
自动优化(索引)Automatic tuning (indexes) Yes NoNo
可用性区域Availability Zones Yes NoNo
Azure 资源运行状况Azure Resource Health Yes NoNo
备份保留Backup retention 可以。Yes. 默认值为7天,最长35天。7 days default, max 35 days. 可以。Yes. 默认值为7天,最长35天。7 days default, max 35 days.
数据迁移服务 (DMS)Data Migration Service (DMS) Yes Yes
文件系统访问File system access 不。No. 使用BULK INSERTOPENROWSET作为替代方法,访问和加载 Azure Blob 存储中的数据。Use BULK INSERT or OPENROWSET to access and load data from Azure Blob Storage as an alternative. 不。No. 使用BULK INSERTOPENROWSET作为替代方法,访问和加载 Azure Blob 存储中的数据。Use BULK INSERT or OPENROWSET to access and load data from Azure Blob Storage as an alternative.
异地还原Geo-restore 是-除超大规模以外的所有服务层Yes - all service tiers other than hyperscale 是-使用Azure PowerShellYes - using Azure PowerShell.
超大规模体系结构Hyperscale architecture Yes NoNo
长期备份保留-从左向右Long-term backup retention - LTR 是,保持自动备份最多10年。Yes, keep automatically taken backups up to 10 years. 还不可以。Not yet. 使用 @no__t 0手动备份作为临时解决方法。Use COPY_ONLY manual backups as a temporary workaround.
暂停/继续Pause/resume 是,在无服务器模型Yes, in serverless model NoNo
基于策略的管理Policy-based management NoNo NoNo
公共 IP 地址Public IP address 可以。Yes. 可使用防火墙或服务终结点限制访问。The access can be restricted using firewall or service endpoints. 可以。Yes. 需要显式启用端口3342,且必须在 NSG 规则中启用。Needs to be explicitly enabled and port 3342 must be enabled in NSG rules. 如果需要,可以禁用公共 IP。Public IP can be disabled if needed. 有关更多详细信息,请参阅公共终结点See Public endpoint for more details.
数据库时间点还原Point in time database restore 是-除超大规模以外的所有服务层-请参阅SQL 数据库恢复Yes - all service tiers other than hyperscale - see SQL Database recovery 是 - 请参阅 SQL 数据库恢复Yes - see SQL Database recovery
资源池Resource pools 是,作为弹性池Yes, as Elastic pools 可以。Yes. 单个托管实例可以有多个共享同一资源池的数据库。A single managed instance can have multiple databases that share the same pool of resources. 此外,还可以在可共享资源的实例池(预览版)中部署多个托管实例。In addition, you can deploy multiple managed instances in instance pools(Preview) that can share the resources.
增加或减少(联机)Scaling up or down (online) 是的,你可以更改 DTU 或保留的 Vcore 或最大停机时间,但停机时间最短。Yes, you can either change DTU or reserved vCores or max storage with the minimal downtime. 是的,你可以更改保留的 Vcore 或最大的存储,但停机时间最短。Yes, you can change reserved vCores or max storage with the minimal downtime.
SQL 别名SQL Alias 否,使用DNS 别名No, use DNS Alias 否,使用Clicongf在客户端计算机上设置别名。No, use Clicongf to set up alias on the client machines.
SQL AnalyticsSQL Analytics Yes Yes
SQL 数据同步SQL Data Sync Yes NoNo
SQL Server Analysis Services (SSAS)SQL Server Analysis Services (SSAS) 不是, Azure Analysis Services是单独的 Azure 云服务。No, Azure Analysis Services is a separate Azure cloud service. 不是, Azure Analysis Services是单独的 Azure 云服务。No, Azure Analysis Services is a separate Azure cloud service.
SQL Server Integration Services (SSIS)SQL Server Integration Services (SSIS) 是,使用 Azure 数据工厂 (ADF) 环境中的托管 SSIS ,其中程序包存储在由 Azure SQL 数据库承载的 SSISDB 中并在 Azure SSIS 集成运行时 (IR) 上执行,请参阅在 ADF 中创建 Azure-SSIS IRYes, with a managed SSIS in Azure Data Factory (ADF) environment, where packages are stored in SSISDB hosted by Azure SQL Database and executed on Azure SSIS Integration Runtime (IR), see Create Azure-SSIS IR in ADF.

若要比较 SQL 数据库服务器和托管实例中的 SSIS 功能,请参阅比较 AZURE SQL 数据库单一数据库、弹性池和托管实例To compare the SSIS features in SQL Database server and Managed Instance, see Compare an Azure SQL Database single database, elastic pool, and managed instance.
是,使用 Azure 数据工厂 (ADF) 环境中的托管 SSIS ,其中程序包存储在由托管实例承载的 SSISDB 中并在 Azure SSIS 集成运行时 (IR) 上执行,请参阅在 ADF 中创建 Azure-SSIS IRYes, with a managed SSIS in Azure Data Factory (ADF) environment, where packages are stored in SSISDB hosted by Managed Instance and executed on Azure SSIS Integration Runtime (IR), see Create Azure-SSIS IR in ADF.

若要比较 SQL 数据库和托管实例中的 SSIS 功能,请参阅比较 AZURE SQL 数据库单一数据库、弹性池和托管实例To compare the SSIS features in SQL Database and Managed Instance, see Compare an Azure SQL Database single database, elastic pool, and managed instance.
SQL Server Reporting Services (SSRS)SQL Server Reporting Services (SSRS) 否 - 请参阅 Power BINo - see Power BI 否 - 请参阅 Power BINo - see Power BI
查询性能见解(QPI)Query Performance Insights (QPI) Yes 不。No. 使用 SQL Server Management Studio 和 Azure Data Studio 中的内置报表。Use built-in reports in SQL Server Management Studio and Azure Data Studio.
VNetVNet Partial,它使用VNet 终结点启用受限访问Partial, it enables restricted access using VNet Endpoints 是的,托管实例注入到客户的 VNet 中。Yes, Managed Instance is injected in customer's VNet. 请参阅子网VNetSee subnet and VNet
VNet 服务终结点VNet Service endpoint Yes NoNo
VNet 全局对等互连VNet Global peering 是,使用专用 IP 和服务终结点Yes, using Private IP and service endpoints 不能,由于VNet 全局对等互连中的负载均衡器约束不支持托管实例No, Managed Instance is not supported due to Load balancer constraint in VNet global peering.

工具Tools

Azure SQL 数据库支持可帮助你管理数据的各种数据工具。Azure SQL database supports various data tools that can help you to manage your data.

工具Tool 单一数据库和弹性池Single databases and elastic pools 托管实例和实例池Managed instances and instance pools
Azure 门户Azure portal Yes Yes
Azure CLIAzure CLI Yes Yes
Azure Data StudioAzure Data Studio Yes Yes
Azure PowerShellAzure Powershell Yes Yes
BACPAC 文件(导出)BACPAC file (export) 是 - 请参阅 SQL 数据库导出Yes - see SQL Database export 是 - 请参阅 SQL 数据库导出Yes - see SQL Database export
BACPAC 文件(导入)BACPAC file (import) 是 - 请参阅 SQL 数据库导入Yes - see SQL Database import 是 - 请参阅 SQL 数据库导入Yes - see SQL Database import
Data Quality Services (DQS)Data Quality Services (DQS) NoNo NoNo
Master Data Services (MDS)Master Data Services (MDS) NoNo NoNo
SMOSMO Yes 版本 150Yes version 150
SQL Server Data Tools (SSDT)SQL Server Data Tools (SSDT) Yes Yes
SQL Server Management Studio (SSMS)SQL Server Management Studio (SSMS) Yes 版本18.0 和更高版本Yes version 18.0 and higher
SQL Server PowerShellSQL Server PowerShell Yes Yes
SQL Server ProfilerSQL Server Profiler 否 - 请参阅扩展事件No - see Extended events Yes
System Center Operations Manager (SCOM)System Center Operations Manager (SCOM) Yes 是,在预览中Yes, in preview

迁移方法Migration methods

你可以使用不同的迁移方法在 SQL Server、单一数据库和托管实例数据库之间移动数据。You can use different migration methods to move your data between SQL Server, Single Database, and Managed Instance databases. 在运行迁移时,某些方法处于联机状态,并且选取在源上进行的所有更改,而在脱机方法中,你需要在迁移过程中停止正在修改源数据的工作负荷。Some methods are Online and picking-up all changes that are made on the source while you are running migration, while in Offline methods you need to stop your workload that is modifying data on the source while the migration is in progress.

Source 单一数据库和弹性池Single database and elastic pool 托管实例和实例池Managed Instance and instance pools
SQL Server (本地、Add-azurevm、Amazon RDS)SQL Server (on-prem, AzureVM, Amazon RDS) 联机: 数据迁移服务(DMS)事务复制Online: Data Migration Service (DMS), Transactional Replication
脱机: BACPAC 文件(导入),BCPOffline: BACPAC file (import), BCP
联机: 数据迁移服务(DMS)事务复制Online: Data Migration Service (DMS), Transactional Replication
脱机: 本机备份/还原, BACPAC 文件(导入),BCP,快照复制Offline: Native backup/restore, BACPAC file (import), BCP, Snapshot replication
单个数据库Single database 脱机: BACPAC 文件(导入),BCPOffline: BACPAC file (import), BCP 脱机: BACPAC 文件(导入),BCPOffline: BACPAC file (import), BCP
托管实例Managed Instance 联机: 事务复制Online: Transactional Replication
脱机: BACPAC 文件(导入)、BCP、快照复制Offline: BACPAC file (import), BCP, Snapshot replication
联机: 事务复制Online: Transactional Replication
脱机: 跨实例时间点还原(Azure PowerShellAzure CLI)、本机备份/还原BACPAC 文件(导入)、BCP、快照复制Offline: Cross-instance point-in-time restore (Azure PowerShell or Azure CLI), Native backup/restore, BACPAC file (import), BCP, Snapshot replication

后续步骤Next steps

Microsoft 会继续向 Azure SQL 数据库添加功能。Microsoft continues to add features to Azure SQL Database. 访问针对 Azure 的服务更新网页,并使用以下筛选器获取最新更新:Visit the Service Updates webpage for Azure for the newest updates using these filters:

有关 Azure SQL 数据库风格的详细信息,请参阅:For more information about the Azure SQL Database flavors, see: