bersx.blogg.se - Configuring excel for redshift data warehouse

Configuring excel for redshift data warehouse driver#
Configuring excel for redshift data warehouse archive#
Configuring excel for redshift data warehouse full#

The final step in terms of cluster configuration was to configure a list of IPs that were authorised to access the cluster. This is handled from within the security screen on the Redshift Management Console. We used the public IP of the Leader node for our inbound client connections. Clicking the Cluster Name hyperlink will show you a summary screen, detailing security config, cluster status, information about backups and URLs for connecting to your cluster.Īt the bottom of the screen area list of public and private IPs for the Leader and Compute Nodes of the cluster: The important thing to note here is that as soon as the cluster is launched and running, you will be start being charged.Īfter you click Launch, the cluster build will begin, and after some time the Status will switch from creating to Available. The next configuration screen allows you to set various security and network options:įinally you are presented with a summary screen confirming your configuration options. For our test case, we opted for a two node cluster (which in fact has 3 nodes - 1 Leader node and 2 Compute nodes): Leaving the database name blank will create a database named 'dev’.Īfter clicking Continue, the next page allows you to size your cluster. From here, fill out the cluster details, for example: From the Redshift page, select a Region, and then Launch Cluster. You deploy a Redshift database from the AWS management console. Once the bucket has been created, you then need to create a folder within this, in this instance the folder was named ORA_STG. In order to create this, browse to the S3 section of the AWS Console, and click Create Bucket. The Attunity CloudBeam service initially stages files in an S3 bucket before loading into the target database schema. It's at this point you may want to touch base with your resident DBA :) Optionally create a dedicated database account for Attunity - requires select privs on various V$ tables, the GL schema tables and execute on the LogMiner packages.

Configuring excel for redshift data warehouse archive#

Switch the database into archive log mode.

Configuring excel for redshift data warehouse full#

Add supplemental logging (for this experiment full logging was added on the GL tables).

The database requirements for Attunity Replicate are: In particular, we used the GL schema as this housed some sizeable data. The source RDBMS used for this proof of concept was an Oracle EBS database running on 11.1.0.7.

Amazon S3 - Amazon's cloud storage service, which is used by Attunity to stage replication/change data prior to loading into the Redshift database.

In order to replicate data to Redshift, you need to set up an account with Attunity and then sign up for a CloudBeam subscription. Attunity supports on going source to target replication as well as storing change data in audit / change tracking tables.

Attunity Replicate & Cloudbeam - Attunity provide log based Change Data Capture and replication functionality, which includes Redshift as a target database.

Based on ParAccel technology (which itself has roots in PostGresQL), the service utilises MPP, columnar storage and compression principles to enhance query performance.

Amazon Redshift - Amazon's Fully Managed Data Warehouse in the cloud offering.

The diagram below shows the architecture we went with at the start of the project.Ī little about the non-Oracle components: What gave us hope though was that Redshift uses Postgres-compatible ODBC and JDBC drivers, and we got it working with OBIEE a few months ago, so the premise for the PoC seemed reasonable to us. It’s important to understand what “not supported” or “not certified” means in this context - it doesn’t mean it won’t work, it just means you’re on your own if it doesn’t. They were also interested in trying out Attunity Replicate with Cloudbeam as the CDC solution, a product conceptually similar to Oracle GoldenGate but hosted on the Amazon AWS platform, and licensed by data volume and month rather than per CPU, perpetual, as GoldenGate is.īecause the client is a big user of Oracle ETL technology though - currently OWB, moving to ODI in the near future - they still wanted to use ODI to do the main data integration work, so an interesting question for us was whether ODI was a suitable tool for use with Redshift, which isn’t an officially supported source or target platform for ODI. Oracle on-premise, or using Amazon RDS, and they were also interested in the potential performance benefits of running their data warehouse on a column-store database.

Configuring excel for redshift data warehouse driver#

The main driver for this was the economics of running Redshift in the cloud vs. One of our longstanding Oracle customers recently asked us to put together a proof-of-concept DW system using Amazon Redshift as the data warehouse database, rather than Oracle Database.