Re: Sample ETL Advice

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Allan Mitchell <allan@xxxxxxxxxxxxxxxxxx>
Date: Thu, 02 Feb 2006 07:44:01 -0800

Hello imani_technology_spam@xxxxxxxxx,

I am saying that TSQL will pound for pound be the best option but it may not be the best thing if you want complex scrubbing. Keep it simple. SSIS is a hammer but not everything is a nail.

TSQL is very very performant when used properly and well. SSIS is likewise.

Allan

That's very interesting. Again, we found that it was much more
efficient and flexible to use T-SQL within stored procedures to
complete our ETL tasks when the source and destination are both SQL
Server 2000. Can I assume that approach might not be necessary with
SQL Server 2005 or that SSIS can get the job done more efficiently
that stored procedures?

Follow-Ups:
- Re: Sample ETL Advice
  - From: imani_technology_spam

References:
- Re: Sample ETL Advice
  - From: imani_technology_spam

Prev by Date: Re: DTS transfer from Paradox to SQL Server 2000 using SQL Agent
Next by Date: migrate + convert data from old to new db structure in SQL 2000 with DTS
Previous by thread: Re: Sample ETL Advice
Next by thread: Re: Sample ETL Advice
Index(es):
- Date
- Thread

Relevant Pages

Re: Merge Join Question
... You can use TSQL from within SSIS, you do not need to go all procedural and row based. ... In the Merge Join you are joining on CustomerID on each sorted input? ... INNER JOIN Sales.CustomerAddress ...
(microsoft.public.sqlserver.dts)
Re: SQL 2008: E-Mail verschicken, wenn =?ISO-8859-1?Q?Datens=E4t?= =?ISO-8859-1?
... wenn in einer bestimmten Tabelle Datensätze drin ... Es geht allerdings auch bestimmt bequem über TSQL bzw SSIS. ... Ich möchte möglichst auf Tools verzichten. ...
(microsoft.public.de.sqlserver)