Hi:

I am using a Transform Data Task to bring data from a Sybase database
to SQL server. I was just bringing the all the fields and rows into SQL
Server, but then decided I wanted to use a WHERE and ORDER BY Clause,
so I changed the transform data task to use an SQL query instead. There
are these results:

1. When I close the Transform Data task (or Parse the query), it hangs
for a very long time.
2. Running the package now takes longer. Shouldn't the WHERE clause
speed things up?
3. I am using an Active X script task to dynamically set the tablename
in Sybase at runtime (I have to append the date i.e. 20041031 to the
table name). It doesn't work when I use a query instead of just
pointing to a table. Shouldn't the source table property in the Data
Pump Task be equal to the table referenced in the "FROM" clause?
Shouldn't setting that property in my Active X script task go into the
query and change the FROM clause?
Thanks for the help, I'm pretty new at this,
Kayda

Comments inline-

<shop (AT) pacifictabla (DOT) com> wrote


all data accross, and if the where clause is not very restrictive this may
not be the case, or if this is a large table and the where clause induces a
table scan. How fast is the query just run directly on the source system?
Why do you need a sort? Not normally required, unless perhaps you are using
fast load into indexed table, but this requires carefull planning.

The set a query you set the SourceSQLStatement property. The "source table
property" is I assume the SourceObjectName property, which will be ignored
if the SourceSQLStatement is also supplied, so to change the table name
dynamically you need to change the complete SQL string in
SourceSQLStatement.


--
Darren Green
http://www.sqldts.com