Search This Blog

Data Converse

It is a truth very certain that when it is not in our power to determine. What is true we ought to follow what is most probable. —Descartes - “Discourse on Method” ----------- I am a master student and always curious to work with data to drive some meaningful insights. I use this platform to share my 2 cents of knowledge and recent works in brief blog posts. I would love to get connected with data enthusiasts, please add my contact on LIn (https://goo.gl/mGdB4y) or email me at rchin001@odu.edu.

Informatica Architecture !

Get link
Facebook
X
Pinterest
Email
Other Apps

June 07, 2015

source: Click here for source page.

Get link
Facebook
X
Pinterest
Email
Other Apps

Comments

Time Series Decomposition

May 22, 2017

A time series decomposition is a mathematical procedure which transform a original time series into 3 sub-time series. Seasonal: Patterns which repeat with fixed period of time. User page visits to a website increases in the weekends, so a seasonality of 7 days is observed. Trend: Underlying trend of metrics like User page visit count. Random: Residual of time series after allocation into seasonal and trends time series. There are two types of decomposition: Additive and Multiplicative. They have to be chosen correctly for successful decomposition. Additive: The magnitude of seasonality remains constant when time series increases. Time series = Seasonal + Trend + Random Multiplicative: The magnitude of seasonality varies constantly with time series. Time series = Trend * Seasonal *Random

INFA vs. ODI Market Facts

April 29, 2016

I truly believe Informatica is most refined ETL tool in the martket today, but ODI is giving a tough competition with newly added features in 12c, aggressive marketing of ORACLE offering ODI as an embed product within their products.

Using DEFAULT clause for populating Surrogate Keys

July 07, 2016

In Oracle Database 12 c , a suite of improvements has been implemented around the DEFAULT clause for table columns. A sequence value can now be assigned as the default value for a column. With one simple command, we can remove the need for triggers for populating Surrogate Keys. Creating a DB Trigger: SQL> create or replace 2 trigger TRG_SALES_SURROGATE_KEY 3 before insert on SALES 4 for each row 5 begin 6 :new.SALE_SEQ := SEQ_SALES.nextval; 7 end; 8 / Trigger created. Inserting 10 million rows for testing the Insert time. SQL> insert /*+ APPEND */ into SALES 2 select rownum, ... 3 from 4 ( select 1 from dual connect by level <= 10000 ), 5 ( select 1 from dual connect by level <= 1000 ) 6 / 10000000 rows created. Elapsed: 00:06:3...