March 9, 2009 at 2:20 pm
Just curios how (EIW) works behind the scene?
Let say I would like to copy data (a lot) from one table to another on the same DB.
I can run EIW remotely from my PC or locally from inside sql server.
It seems to me that there is big difference in performance in 2 cases.
This is the reason why I am curios how this stuff works?
Thanks,
March 9, 2009 at 2:31 pm
It builds a package in Integration Services. You can save it and then open it up in BIDS.
March 9, 2009 at 2:36 pm
Steve, sorry I probably was not clear- why there is a big difference in performance while running Wizard locally or remotely? It seems when it's running remotely (i.e. started from my PC) there is extra job involved if I am correct. I try to understand what kind of job is it? Thanks,
March 9, 2009 at 4:37 pm
If it works the way the DTS wizard works in SQL 2000, the data actually is routed through your workstation when you run the wizard from there, but it stays on the server when you run it on the server. That's why big imports or exports should be run on the server.
Greg
March 9, 2009 at 5:06 pm
Greg, Can you please clarify what you meant "data actually is routed through your workstation"?
I can not believe :w00t: that when you copy data from one disk to another on the same server/DB Wizard 1) copies data to your machine and only 2) copies back to server to another disk?
What a waste of resources! And Sql server 2005 is not better in this way?! Thanks
March 10, 2009 at 9:28 am
What I mean is the Wizard will run on the machine where the program that starts it resides. So, if you run it on your workstation, the Wizard runs there. If you run it in a Remote Desktop Connection or from the server console, the Wizard runs on the server.
In DTS, when the Wizard was run on the workstation, it routed the data from the source database, through the workstation, to the destination database. I don't know for sure that it works that way with the SSIS Wizard, but I suspect it might.
Greg
March 10, 2009 at 9:34 am
Greg is correct. When you run the wizard from your WS, it executes locally, calls data from the server, transfers to your WS, processes, sends back to the server. That depends on how your wizard runs. Could export to your disk.
If you run a package from the server, using Agent or a schedule, it runs completely on the server.
If you have specific slowdowns, give us more details and we'll try to help debug what's happening.
March 10, 2009 at 11:15 am
Thanks, gents, for your help
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply