all groups > sql server data warehouse > november 2003 >
You're in the

sql server data warehouse

group:

ETL ideas


ETL ideas kildenc NO[at]SPAM hotmail.com
11/17/2003 1:52:49 PM
sql server data warehouse:
Hi everyone,

I am currently developing an ETL process for a small data warehouse.
Because of its size, it doesn't warrant buying an ETL tool. My
question deals mainly with column and table mappings. Basically, we
have events that are piled in from various machines that track
financial data as well as user actions. Each one of these events has
an operational integer key. Depending on this key, the data gets
inserted into a certain fact table, for example, billpayment. I know I
can brute force this all with sql but I am trying to come up with a
design that makes this dynamic for the addition of future events. I
was thinking about making meta data tables that associate an event
with a certain fact table and then just run the insert. The problem is
that I then must create an sp for every fact table unless I use
dynamic sql. Events also need to be associated with type 2 dimension
tables. I was hoping to come up with a design that would map an
EventID with a dimension table column which is definitely doable not
not very dynamic. Our OLTP is relatively simple. All data from our
production system is inserted into a table with these columns:

AppEventID identitycolumn,
AppID int,
AppEventvalue varchar(500),
DateStamp datetime
additional columns .......

Basically the data gets pumped into this table and I have to direct
and type cast the AppEventvalues to a certain fact table based on an
eventID. Does anybody have any experience is creating a successful
dynamic staging application in this manner and would you recommend
doing it this way. Flexibility is a very important part of this and I
am trying to come up with the most efficient way. Any ideas would be
great. Thanks

BTW, I will be using T-SQL and DTS on SQL server 2000 for all
operations.

Re: ETL ideas Mark Andrews
12/6/2003 9:45:43 PM
Without knowing specifics and not sure if you should have all these fact
tables
I would say the "write one sp for each fact table" and "write one routine to
create
the staging tables that drive these fact tables"

Also I would code it without using DTS if possible. Having just removed all
the DTS
from our ETL process because of little weird things that happen when DTS
runs in production for
months at a time. Linked servers and SQL code work better.

HTH,
Mark
[quoted text, click to view]

AddThis Social Bookmark Button