March 18, 2010 at 12:11 pm
How can this we be done? We have a simple sql query that generates a result set I want to send to a table.
Barkingdog
March 18, 2010 at 12:16 pm
March 18, 2010 at 12:22 pm
Why do you want to use SSIS for this? A simple insert into, select will do right?
If you have to in SSIS, then have dataflow task with oledb source and destination as sql server for source and destination map it.
-VG
March 18, 2010 at 12:37 pm
Before saying "don't use SSIS for this" you need to ask more questions. The biggest one is how much data are we talking about?
Lets say 100,000 rows. I can almost guarantee that SSIS will copy that data faster.
CEWII
March 18, 2010 at 12:46 pm
VG-619426 (3/18/2010)
Why do you want to use SSIS for this? A simple insert into, select will do right?If you have to in SSIS, then have dataflow task with oledb source and destination as sql server for source and destination map it.
-VG
Agreed on the how - just put the query directly into the source, then map it to the destination.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
March 18, 2010 at 12:50 pm
Elliott W (3/18/2010)
Before saying "don't use SSIS for this" you need to ask more questions. The biggest one is how much data are we talking about?Lets say 100,000 rows. I can almost guarantee that SSIS will copy that data faster.
CEWII
If you mean 100,000 from one server to another, then yes, SSIS can be rather fast compared to T-SQL. On the same server though, straight t-SQL inserts would tend to be faster IMO.
That said - for that little - it won't matter much one way or the other.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
March 18, 2010 at 1:35 pm
Matt Miller (#4) (3/18/2010)
Elliott W (3/18/2010)
Before saying "don't use SSIS for this" you need to ask more questions. The biggest one is how much data are we talking about?Lets say 100,000 rows. I can almost guarantee that SSIS will copy that data faster.
CEWII
If you mean 100,000 from one server to another, then yes, SSIS can be rather fast compared to T-SQL. On the same server though, straight t-SQL inserts would tend to be faster IMO.
That said - for that little - it won't matter much one way or the other.
Some of my recent experiences indicate that even with 100,000 records I was getting better performance using SSIS. Mileage may vary..
CEWII
March 18, 2010 at 1:43 pm
Elliott W (3/18/2010)
Matt Miller (#4) (3/18/2010)
Elliott W (3/18/2010)
Before saying "don't use SSIS for this" you need to ask more questions. The biggest one is how much data are we talking about?Lets say 100,000 rows. I can almost guarantee that SSIS will copy that data faster.
CEWII
If you mean 100,000 from one server to another, then yes, SSIS can be rather fast compared to T-SQL. On the same server though, straight t-SQL inserts would tend to be faster IMO.
That said - for that little - it won't matter much one way or the other.
Some of my recent experiences indicate that even with 100,000 records I was getting better performance using SSIS. Mileage may vary..
CEWII
I agree with Elliott - it depends. I have seen it both sides of the fence on the server (better and worse than straight t-sql). Some of it will have to do with how it is written and what is being performed.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply