January 18, 2010 at 1:49 pm
[font="Comic Sans MS"]
Sorry - I am unable understand the problem you are facing here.
Are you looking forward to optimize your Exec SQL task?
If yes - how long does it take if you execute the underlying query on production server?
Are you sure that there is no network/connection setting problem for the exec sql task on your 'prod' environment ? You can easily check this by having a test Exec SQL task that returns - something like : select * from sysobjects ...
[/font]
and see how long it takes ..
[font="Comic Sans MS"]--
Sabya[/font]
January 19, 2010 at 2:09 pm
Hi,
If you trying to transfer data, you can use the Data Flow task to transfer data from table(s) in database to the target database.
you can run the sql in the exec sql task on the actual database to see how it performs and tune it if needed.
January 19, 2010 at 2:40 pm
gurukiran.bhat (1/18/2010)
I would like to mention that we are using exicute SQL task to bring data from source
How much data are you trying to move?
Is there a reason why you chose to use the ExecuteSQL task over a Data Flow?
Viewing 3 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply