(Mark Gillis) Part 1 was a basic illustration of how INGEST can be used to provide a high-availability data replication mechanism without employing expensive and complicated ETL. In Part 2, I’m going to try and explore a few more complicated options: enriching or extending the data as it is ingested
Read More - Register for Free Membership
SQL Server, Azure SQL Database, Amazon RDS & AWS, Oracle and IBM Help