Skip to content

Latest commit

 

History

History
51 lines (38 loc) · 3.31 KB

non-sql-server-publishers.md

File metadata and controls

51 lines (38 loc) · 3.31 KB
title description author ms.author ms.date ms.service ms.subservice ms.topic ms.custom helpviewer_keywords
Non-SQL Server Publishers
Non-SQL Server Publishers
MashaMSFT
mathoma
09/25/2024
sql
replication
conceptual
updatefrequency5
heterogeneous database replication, non-SQL Server Publishers
non-SQL Server Publishers
heterogeneous data sources, non-SQL Server Publishers
Publishers [SQL Server replication], Oracle

Non-SQL Server Publishers

[!INCLUDE SQL Server]

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.

Related content