Hi. My name is Susan Long, and I'm a solutions architect with the Dell Software Group. Today, I'll be presenting to you SharePlex's capability to replicate from Oracle to SQL Server, as well as eight other targets. SharePlex has been known to replicate from Oracle to Oracle for many years since 1998. SharePlex now supports eight target systems to date and more to come in the future. With this capability to replicate from Oracle to SQL Server, the following configurations are now supported
You can now offload reporting from an Oracle production database to a near real time SQL Server database replicating all or a subset of data by table, row, and or column. You can consolidate data from multiple Oracle instances to essential SQL Server target or distribute Oracle data to multiple SQL Server databases. You can integrate applications that run Oracle and SQL Server backends with SharePlex keeping the data near real time. Migrating an Oracle database to SQL Server can be done with minimal system and business impact.
SharePlex architecture for Oracle to SQL Server is the same as for Oracle to Oracle with these same queues and processes. The post process connects to the SQL Server instance via ODBC. The configuration file which tells SharePlex what to replicate and to where is slightly different to using an r notation in the routing now rather than an o, which would depict Oracle.
Let's go ahead and go to the lab now, where you can see that the SQL Server config file is active. If we take a look at that config file, we can see that we're replicating from an Oracle instance depicted by o.. The Sid name is olri10, and we're replicating to a target, which is SQL Server. We can see that because it's depicted by the r., and instead of an Oracle Sid, we now have the SQL Server database.
But you can see that the commands are the same. We would use the Status command to see the processes that are running, Capture, Reader, and Export because, this is the source. And we can also use the queue Status command, where here we can see the Capture queue and the Export queue. Again, because this is the source.
Now let's go ahead and insert a row into the Oracle database. We're going to insert this row Billy Joel. Go ahead and commit that. And now let's go to the target, SQL Server, and we'll go ahead and see that that row appears. We'll go ahead and refresh and into that SharePlex db SQL Server database, the DEMO DEST table. We go ahead and Execute that query and now we can see there's the Billy Joe row in the table.
Now note that we can use those same commands, status command to see the import and post process since it's on the target, qstatus, and we see the post queue Also note that we see similar utilities for Oracle where MSS cleansp and MSS setup are analogous to ora cleansp and ora setup for Oracle where these utilities are used to clean a SharePlex installation or create the SharePlex database user.
SharePlex can replicate to an ODBC compliant database. What will determine which ODBC compliant databases are supported will be the test results from the ODBC test suite utility called OTS. This utility simulates transactions that SharePlex should be able to post, send, or apply to the target database. OTS will verify the results that are as expected. Upon success at this level SharePlex Product Management would then take into account market viability and make the decision support of the database.
OTS is available in the SharePlex community. In addition, SharePlex can replicate to file either SQL format or XML format and also to a JMS queue. To learn more about SharePlex please visit our website at www.DellSoftware.com/SharePlex.