Oracle Autonomous Data Warehouse
Oracle Autonomous Data Warehouse ETL connector for data replication
Last updated
Daton
Oracle Autonomous Data Warehouse ETL connector for data replication
Last updated
Once the sign up process is complete, you will be taken to the cloud dashboard.
Enter the basic parameters for the database and which compartment you'd like the data warehouse to run.
There are two Oracle autonomous database services that oracle provides under its autonomous umbrella. A Oracle database tuned for data warehousing and another data tuned for transaction processing. Although both these databases run on Oracle's high-end Exadata converged infrastructure, these databases are tuned to perform specific functions exceptionally well.
Unless you require a dedicated Exadata server to run your data warehousing workloads, select the serverless option and let Oracle manage all aspects of running the data warehouse for you.
An OCPU in the Oracle cloud world is a full intel X86 core, not a virtual core as is the case in most public clouds. It is an important differentiation as it impact both the performance and the price of the offering. Please be aware of this which comparing costs with other database services. Typically you'd have to apply a 2:1 multiple, i.e 2 vCPUs = 1 OCPU.
Create an admin user to kick start things. The other parameters, BYOL and License Included options are there to support Oracle's existing customers as well as new customers.
If you have existing database licenses that you would like to use for the cloud, you can select the BYOL options. Please consult your Oracle sales team to understand this model and its implications better. The license included version is the default version one should pick if they don't intend to leverage their existing investment in Oracle towards Autonomous database services.
Once the data warehouse is created, you will have access to the credentials needed to connect Daton to the Autonomous Data Warehouse.
When the database is first created, only the admin user gets created. Go ahead and create an additional user that you can use exclusively to grant access to Daton.
Save the wallet file to your desktop and decide which TNS Name to use. TNS Name will act as your service name in the integration. Refer the documentation to decide whether you want to select the low, medium, or high options.
Daton will use the integration name as the prefix to all the tables that get created in the data warehouse. So, we recommend that you select a short meaningful name to ensure table name lengths in the data warehouse are not too long or breach the maximum length limitations set by the database.
Upload the wallet file that was downloaded from the console along with the service name (TNS Name), username and password.
We recommend that you create a dedicated user and user that username to connect Daton to ADW.
Select the schema in which you would like Daton to replicate data. This schema will act as the staging area from where further transformations can be performed.
Submit the integration and wait for your data to show up.
If you have any questions regarding Daton or having any difficulty using the product, do not hesitate to reach out to us. Our support team is available for you on multiple mediums. You can
Email us at support@sarasanalytics.com
Chat with us using the intercom window in the application.
If you would like to get a demo of Daton, please send us a note at support@sarasanalytics.com.
We strive to make our documentation as clear and legible as possible. But, if you feel there are discrepancies or areas of improvement for us, please send us a note.
