| title | Non-SQL Server Publishers | Microsoft Docs | ||||
|---|---|---|---|---|---|
| ms.custom | |||||
| ms.date | 08/29/2017 | ||||
| ms.prod | sql | ||||
| ms.prod_service | database-engine | ||||
| ms.reviewer | |||||
| ms.technology | replication | ||||
| ms.topic | conceptual | ||||
| helpviewer_keywords |
|
||||
| ms.assetid | 08a160a6-33be-46b5-bc7b-d53180d8bdf1 | ||||
| author | MashaMSFT | ||||
| ms.author | mathoma |
[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md]
Publishing data from non- [!INCLUDEssNoVersion] sources allows you to consolidate data in [!INCLUDEmsCoName] [!INCLUDEssNoVersion]. [!INCLUDEssNoVersion] can subscribe to snapshot or transactional data published from an Oracle database. For more information about publishing from Oracle, see Oracle Publishing Overview.
[!INCLUDEssNoVersion] supports the following heterogeneous scenarios for transactional and snapshot replication:
-
Publishing data from [!INCLUDEssNoVersion] to non-[!INCLUDEssNoVersion] Subscribers.
-
Publishing data to and from Oracle has the following restrictions:
| Replication | 2016 or earlier | 2017 or later |
|---|---|---|
| Replication from Oracle | Only support Oracle 10g or earlier | Only support Oracle 10g or earlier |
| Replication to Oracle | Up to Oracle 12c | Not supported |
Heterogeneous replication to non-SQL Server subscribers is deprecated. Oracle Publishing is deprecated. To move data, create solutions using change data capture and [!INCLUDEssIS].
Caution
[!INCLUDEssNoteDepFutureAvoid]
Publishing from non- [!INCLUDEssNoVersion] databases is ideal for the following scenarios:
| Scenario | Description |
|---|---|
| [!INCLUDEmsCoName] .NET Framework application deployments | Develop with [!INCLUDEmsCoName] Visual Studio and [!INCLUDEssNoVersion] while operating on data replicated from a non-[!INCLUDEssNoVersion] database. |
| Data warehousing staging servers | Keep [!INCLUDEssNoVersion] staging databases synchronized with a non-[!INCLUDEssNoVersion] database. |
| Migration to [!INCLUDEssNoVersion] | Test your application in real time against [!INCLUDEssNoVersion] while replicating the source system's changes. Switch to [!INCLUDEssNoVersion] when satisfied with the migration. |