功能比較: Azure SQL Database 和 Azure SQL 受控執行個體Features comparison: Azure SQL Database and Azure SQL Managed Instance

適用於: Azure SQL Database Azure SQL 受控執行個體

Azure SQL Database 和 SQL 受控執行個體會與最新穩定版本的 SQL Server 共用通用的程式碼基底。Azure SQL Database and SQL Managed Instance share a common code base with the latest stable version of SQL Server. 大部分的標準 SQL 語言、查詢處理和資料庫管理功能都相同。Most of the standard SQL language, query processing, and database management features are identical. SQL Server 和 SQL Database 或 SQL 受控執行個體之間常見的功能如下:The features that are common between SQL Server and SQL Database or SQL Managed Instance are:

Azure 會管理您的資料庫,並保證其高可用性。Azure manages your databases and guarantees their high-availability. 某些可能會影響高可用性或無法在 PaaS 世界中使用的功能,在 SQL Database 和 SQL 受控執行個體中的功能有限。Some features that might affect high-availability or can't be used in PaaS world have limited functionalities in SQL Database and SQL Managed Instance. 下表將說明這些功能。These features are described in the tables below. 如果您需要更多有關差異的詳細資料,您可以在Azure SQL DatabaseAzure SQL 受控執行個體的個別頁面中找到它們。If you need more details about the differences, you can find them in the separate pages for Azure SQL Database or Azure SQL Managed Instance.

SQL Database 和 SQL 受控執行個體的功能Features of SQL Database and SQL Managed Instance

下表列出 SQL Server 的主要功能,並提供 Azure SQL Database 和 Azure SQL 受控執行個體中部分或完全支援該功能的相關資訊,以及有關此功能的詳細資訊連結。The following table lists the major features of SQL Server and provides information about whether the feature is partially or fully supported in Azure SQL Database and Azure SQL Managed Instance, with a link to more information about the feature.

功能Feature Azure SQL DatabaseAzure SQL Database Azure SQL 受控執行個體Azure SQL Managed Instance
一律加密Always Encrypted 是 - 請參閱憑證存放區金鑰保存庫Yes - see Cert store and Key vault 是 - 請參閱憑證存放區金鑰保存庫Yes - see Cert store and Key vault
AlwaysOn 可用性群組Always On Availability Groups 99.99-每個資料庫保證99.995% 的可用性。99.99-99.995% availability is guaranteed for every database. Azure SQL Database 的業務連續性概觀會討論災害復原Disaster recovery is discussed in Overview of business continuity with Azure SQL Database 99.99。保證每個資料庫都有% 的可用性,而且不能由使用者管理99.99.% availability is guaranteed for every database and can't be managed by user. 嚴重損壞修復會在Azure SQL Database 的商務持續性總覽中討論。Disaster recovery is discussed in Overview of business continuity with Azure SQL Database. 使用自動容錯移轉群組,在另一個區域中設定次要 SQL 受控執行個體。Use Auto-failover groups to configure a secondary SQL Managed Instance in another region. SQL Server 實例和 SQL Database 無法當做 SQL 受控執行個體的次要複本使用。SQL Server instances and SQL Database can't be used as secondaries for SQL Managed Instance.
附加資料庫Attach a database No No
稽核Auditing Yes ,但有一些差異Yes, with some differences
Azure Active Directory (Azure AD) 驗證Azure Active Directory (Azure AD) authentication 是。Yes. 僅 Azure AD 使用者。Azure AD users only. 是。Yes. 包括伺服器層級 Azure AD 登入。Including server-level Azure AD logins.
BACKUP 命令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 can't 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 CREATEYes, without access to file system for BACKUP and CREATE operations. 是,不需要存取和作業的檔案系統 BACKUP CREATE -請參閱憑證差異Yes, without access to file system for BACKUP and CREATE operations - see certificate differences.
變更資料捕獲-CDCChange data capture - CDC No Yes
定序 - 伺服器/執行個體Collation - server/instance 否,一律會使用預設伺服器定序 SQL_Latin1_General_CP1_CI_ASNo, default server collation SQL_Latin1_General_CP1_CI_AS is always used. 是,可以在建立實例時設定,而且之後無法更新。Yes, can be set when the instance is created and can't be updated later.
資料行存放區索引Columnstore indexes 是-進階層、標準層-S3 和更新版本、一般用途層、業務關鍵和超大規模資料庫層Yes - Premium tier, Standard tier - S3 and above, General Purpose tier, Business Critical, and HyperScale tiers Yes
Common language runtime-CLRCommon language runtime - CLR No 是,但不能存取語句中的檔案系統 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 Vault和, SHARED 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 No 是,在實例內。Yes, within the instance. 請參閱跨實例查詢的連結伺服器差異See Linked server differences for cross-instance queries.
Database mail-DbMailDatabase mail - DbMail No Yes
資料庫鏡像Database mirroring No No
資料庫快照集Database snapshots No No
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 No Yes
分散式交易 - MS DTCDistributed transactions - MS DTC 否 - 請參閱彈性交易No - see Elastic transactions 否-請參閱連結的伺服器差異No - see Linked server differences. 嘗試在遷移期間,將多個分散式 SQL Server 實例中的資料庫合併成一個 SQL 受控執行個體。Try to consolidate databases from several distributed SQL Server instances into one SQL 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 No
運算式Expressions Yes Yes
擴充事件 (XEvent) Extended events (XEvent) 部分請參閱 SQL Database 中的擴充事件Some - see Extended events in SQL Database 是 - 請參閱擴充事件差異Yes - see Extended events differences
擴充預存程式Extended stored procedures No No
檔案和檔案群組Files and file groups 僅限主要檔案群組Primary file group only 是。Yes. 系統會自動指派檔案路徑,而且無法在語句中指定檔案位置 ALTER DATABASE ADD FILE File paths are automatically assigned and the file location can't be specified in ALTER DATABASE ADD FILE statement.
FilestreamFilestream No No
全文檢索搜尋 (FTS) 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 是- Premium 和業務關鍵層僅限於非持續性記憶體內建物件(例如資料表類型)的有限支援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 DatabaseOnly 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. SQL 受控執行個體意見反應專案上追蹤這些要求Track these requests on SQL Managed Instance feedback item
記錄傳送Log shipping 每個資料庫都包含高可用性High availability is included with every database. 「嚴重損壞修復」將在商務持續性總覽中討論。Disaster recovery is discussed in Overview of business continuity. 原生內建為 Azure 資料移轉服務遷移程式的一部分。Natively built in as a part of Azure Data Migration Service 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. 「嚴重損壞修復」將在商務持續性總覽中討論。Disaster recovery is discussed in Overview of business continuity. 無法當做資料庫之間的複寫機制使用-在業務關鍵層自動容錯移轉群組異動複寫上使用次要複本做為替代方案。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 可以,但是 CREATEALTER login 語句不會提供 (Windows 和伺服器層級 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 No Yes
OLE AutomationOLE Automation No No
OPENDATASOURCEOPENDATASOURCE No 是,僅適用于 SQL Database、SQL 受控執行個體和 SQL Server。Yes, only to SQL Database, SQL Managed Instance and SQL Server. 請參閱t-sql 差異See T-SQL differences
OPENQUERYOPENQUERY No 是,僅適用于 SQL Database、SQL 受控執行個體和 SQL Server。Yes, only to SQL Database, SQL Managed Instance and SQL Server. 請參閱t-sql 差異See T-SQL differences
OPENROWSETOPENROWSET 是,僅適用于從 Azure Blob 儲存體匯入。Yes, only to import from Azure Blob storage. 是,僅適用于 SQL Database、SQL 受控執行個體和 SQL Server,以及從 Azure Blob 儲存體匯入。Yes, only to SQL Database, SQL Managed Instance and SQL Server, 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. 您可以使用函數查詢放在 Azure Blob 儲存體的檔案中的資料 OPENROWSETYou can query data in the files placed on Azure Blob Storage using OPENROWSET function. 否。No. 您可以使用函數查詢放在 Azure Blob 儲存體的檔案中的資料 OPENROWSETYou can query data in the files placed on Azure Blob Storage using OPENROWSET function.
查詢通知Query Notifications No Yes
Machine Learning Services 先前 (R services) Machine Learning Services(Formerly R Services) 是,現已在公開預覽版中推出Yes, in public preview No
復原模式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 No Yes
RESTORE 陳述式RESTORE statements No 是, FROM URL 在 Azure Blob 儲存體上放置備份檔案的強制選項。Yes, with mandatory FROM URL options for the backups files placed on Azure Blob Storage. 請參閱還原差異See Restore differences
從備份還原資料庫Restore database from backup 僅限從自動備份 - 請參閱SQL Database 復原From automated backups only - see SQL Database recovery 從自動備份-請參閱SQL Database復原以及放在 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 受控執行個體中使用的 SQL Server 資料庫引擎版本高於內部部署所使用的任何 RTM 版本 SQL Server。No, because SQL Server database engine used in SQL 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 No No
Service BrokerService Broker No 是,但只能在實例內。Yes, but only within the instance. 如果您使用遠端 Service Broker 路由,請嘗試在遷移期間將數個分散式 SQL Server 實例中的資料庫合併成一個 SQL 受控執行個體,並僅使用本機路由。If you are using remote Service Broker routes, try to consolidate databases from several distributed SQL Server instances into one SQL Managed Instance during migration and use only local routes. 請參閱Service Broker 差異See Service Broker differences
伺服器組態設定Server configuration settings No 是 - 請參閱 T-SQL 差異Yes - see T-SQL differences
Set 語句Set statements 大部分 - 請參閱個別陳述式Most - see individual statements 是 - 請參閱 T-SQL 差異Yes - see T-SQL differences
SQL Server AgentSQL Server Agent 否-請參閱彈性作業 (預覽) No - see Elastic jobs (preview) 是 - 請參閱 SQL Server Agent 差異Yes - see SQL Server Agent differences
SQL Server 稽核SQL Server Auditing 否 - 請參閱 SQL Database 稽核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. 每個資料庫 32-GB 的大小32-GB size per core for every database. 是。Yes. 整個 GP 層的每個 vCore 24 GB 大小,並受限於 BC 層的實例大小24-GB 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 No ,而且必須在建立 SQL 受控執行個體時設定。Yes, and it must be configured when the SQL Managed Instance is created.
追蹤旗標 (機器翻譯)Trace flags No 是,但只有有限的全域追蹤旗標集合。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 No No
Windows Server 容錯移轉叢集Windows Server Failover Clustering 否。No. 提供高可用性的其他技術會包含在每個資料庫中。Other techniques that provide high availability are included with every database. 嚴重損壞修復會在Azure SQL Database 的商務持續性總覽中討論。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 Database 的商務持續性總覽中討論。Disaster recovery is discussed in Overview of business continuity with Azure SQL Database.

平台功能Platform capabilities

Azure 平臺提供一些 PaaS 功能,可新增為標準資料庫功能的額外價值。The Azure platform provides a number of PaaS capabilities that are added as an additional value to the standard database features. 有一些外部服務可與 Azure SQL Database 搭配使用。There is a number of external services that can be used with Azure SQL Database.

平臺功能Platform feature Azure SQL DatabaseAzure SQL Database Azure SQL 受控執行個體Azure SQL Managed Instance
作用中異地複寫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 No
可用性區域Availability Zones Yes No
Azure 資源健康狀態Azure Resource Health Yes No
備份保留期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 Yes
超大規模資料庫架構Hyperscale architecture Yes No
長期備份保留-LTRLong-term backup retention - LTR 是,保持自動備份最多10年。Yes, keep automatically taken backups up to 10 years. 目前還不行。Not yet. 使用 COPY_ONLY 手動備份做為暫時的因應措施。Use COPY_ONLY manual backups as a temporary workaround.
暫停/繼續Pause/resume 是,在無伺服器模型Yes, in serverless model No
以原則為基礎的管理Policy-based management No No
公用 IP 位址Public IP address 是。Yes. 您可以使用防火牆或服務端點來限制存取權。The access can be restricted using firewall or service endpoints. 是。Yes. 需要明確啟用,而且必須在 NSG 規則中啟用埠3342。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 Database復原Yes - all service tiers other than hyperscale - see SQL Database recovery 是 - 請參閱 SQL Database 復原Yes - see SQL Database recovery
資源集區Resource pools 是,身為彈性集區Yes, as Elastic pools 是。Yes. SQL 受控執行個體的單一實例可以有多個共用相同資源集區的資料庫。A single instance of SQL Managed Instance can have multiple databases that share the same pool of resources. 此外,您可以將多個 SQL 受控執行個體實例部署在實例集區中, (預覽) 可以共用資源。In addition, you can deploy multiple instances of SQL Managed Instance in instance pools (preview) that can share the resources.
線上) (相應增加或相應減少Scaling up or down (online) 是,您可以在最短的停機時間內變更 DTU 或保留的虛擬核心或最大儲存體。Yes, you can either change DTU or reserved vCores or max storage with the minimal downtime. 是,您可以在最短的停機時間內變更保留的虛擬核心或最大儲存體。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 No
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 Data Factory (ADF) 環境中的受控 SSIS,其中的套件會儲存於 Azure SQL Database 所裝載的 SSISDB 中,並於 Azure SSIS Integration Runtime (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 Database 和 SQL 受控執行個體中的 SSIS 功能,請參閱比較 SQL Database 與 sql 受控執行個體To compare the SSIS features in SQL Database and SQL Managed Instance, see Compare SQL Database to SQL Managed Instance.
是,使用 Azure Data Factory (ADF) 環境中的受控 SSIS,其中套件會儲存在 SQL 受控執行個體所裝載的 SSISDB 中,並在 Azure SSIS Integration Runtime (IR) 上執行,請參閱在 ADF 中建立 AZURE SSIS IRYes, with a managed SSIS in Azure Data Factory (ADF) environment, where packages are stored in SSISDB hosted by SQL Managed Instance and executed on Azure SSIS Integration Runtime (IR), see Create Azure-SSIS IR in ADF.

若要比較 SQL Database 和 SQL 受控執行個體中的 SSIS 功能,請參閱比較 SQL Database 與 sql 受控執行個體To compare the SSIS features in SQL Database and SQL Managed Instance, see Compare SQL Database to SQL Managed Instance.
SQL Server Reporting Services (SSRS)SQL Server Reporting Services (SSRS) 否 - 請參閱 Power BINo - see Power BI 不會使用Power BI 編頁報表,而是在 Azure VM 上裝載 SSRS。No - use Power BI paginated reports instead or host SSRS on an Azure VM. 雖然 SQL 受控執行個體無法將 SSRS 當做服務執行,但它可以使用 SQL Server 驗證,為安裝在 Azure 虛擬機器上的報表伺服器裝載SSRS 類別目錄資料庫While SQL Managed Instance cannot run SSRS as a service, it can host SSRS catalog databases for a reporting server installed on Azure Virtual Machine, using SQL Server authentication.
查詢效能深入解析 (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 部分,它會使用VNet 端點來啟用限制存取Partial, it enables restricted access using VNet Endpoints 是,SQL 受控執行個體會插入客戶的 VNet 中。Yes, SQL Managed Instance is injected in customer's VNet. 請參閱子網VNetSee subnet and VNet
VNet 服務端點VNet Service endpoint Yes No
VNet 全域對等互連VNet Global peering 是,使用私人 IP 和服務端點Yes, using Private IP and service endpoints 不可以,因為VNet 全域對等互連中的負載平衡器條件約束,所以不支援 SQL 受控執行個體No, SQL Managed Instance is not supported due to load balancer constraint in VNet global peering.

工具Tools

Azure SQL Database 和 Azure SQL 受控執行個體支援各種資料工具,可協助您管理資料。Azure SQL Database and Azure SQL Managed Instance support various data tools that can help you manage your data.

工具Tool Azure SQL DatabaseAzure SQL Database Azure SQL 受控執行個體Azure SQL Managed Instance
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 Database 匯出Yes - see SQL Database export 是-請參閱SQL 受控執行個體匯出Yes - see SQL Managed Instance export
BACPAC 檔案 (匯入)BACPAC file (import) 是 - 請參閱 SQL Database 匯入Yes - see SQL Database import 是-請參閱SQL 受控執行個體匯入Yes - see SQL Managed Instance import
Data Quality Services (DQS)Data Quality Services (DQS) No No
Master Data Services (MDS)Master Data Services (MDS) No No
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、Azure SQL Database 和 Azure SQL 受控執行個體之間移動資料。You can use different migration methods to move your data between SQL Server, Azure SQL Database and Azure SQL Managed Instance. 在執行遷移時,某些方法會在線上,並會挑選在來源上所做的所有變更,而在離線方法中,您需要在進行遷移時,停止修改來源上資料的工作負載。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.

SourceSource Azure SQL DatabaseAzure SQL Database Azure SQL 受控執行個體Azure SQL Managed Instance
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
SQL 受控執行個體SQL 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 Database 新增功能。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 Database 和 Azure SQL 受控執行個體的詳細資訊,請參閱:For more information about Azure SQL Database and Azure SQL Managed Instance, see: