"you will never have to write a line of code with SSIS." yeah, MS never lies!
Main Topics
Browse All TopicsI have what I believe shoud be a typical ETL problem. I am incrementally loading a data warehouse. My load data is approximately 100K rows and is an SSIS in memory object at the point I want to load it. My base (Fact) table is 45,000K rows.
My problem is my load data contains both inserts and updates - so I need to upsert it. My question is what is the best way to approach.
I have tried an SSIS lookup on the base table - but I observe SSIS cachiing the data up until it reaches 12 million rows - at which point the package crashes.
I have considered an SSIS merge - but the documentation I am reading tells me this is to merge in memory objects, not one in memory object into an existing table. (And per the above - 45 million rows in memory does not appear to be a good idea.)
I have considered defining a real load table, and upserting using T-SQL - but that violates the premise "you will never have to write a line of code with SSIS." (Not that Microsoft has never lied to us before.)
If anyone has some solid guidence on how to approach this, I would appreciate it. Please be as specific as possible.
Thanks in advance.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: CGLuttrellPosted on 2009-11-05 at 11:25:20ID: 25752952
We addressed something like this on this question, http://www.experts-exchang e.com/Micr osoft/Deve lopment/MS -SQL- Serve r/SQL-Serv er-2005/Q_ 24859315.h tml?sfQuer yTermInfo= 1+ssi+ upse rt , does that help any?
can you structure it into 2 pieces where you update existing rows and then insert the new ones? That might eliminate the caching problem.