Hi Guys
I am trying to do the following and am quite new to SSIS.
I have to select a dataset from a database on server A, check if it exists on server B and perform an Update or Insert dependant on the existence.
I have created a SQL task to do the Select from server A with the results set passed to a variable of Vendors. I have added a ForEach Loop container with an enumerator of Foreach ADO Enumerator and the source variable is set to Vendors.
I have created 2 variables in the Foreach Loop called Code and Supplier - both as strings - as there are 2 fields from the initial Select that need to be passed to the final Update/ Insert.
I have then created another SQL task insert the Foreach which will perform the Update/Insert.
obviously when I run it at the moment it performs the Update/ Insert but just adds the rows with both Code and Supplier as NULL.
having looked at a couple of examples in books I have i know i need to add something in the Expressions of the Update/Insert SQL task but it is here i get a bit lost.
Which of the properties from the drop down do i need to use to map the variables against?
Any help would be massively appreciated asI am tearing my hair out!
Thanks
Scott
Hi Scott,
We're all still learning SSIS. 
It sounds like you're most of the way there.
There are a couple ways to approach this solution. The simplest way, from what I understand from your post, is to use placeholders and parameters in your Update/Insert statements. If you already have the Code and Supplier variables defined, you could perform an insert using an Execute SQL Task with something similar to the following code:
Code Snippet
INSERT INTO Vendors
(Code, Supplier)
VALUES(?, ?)
You could then supply Parameters:
Code Snippet
VariableName Direction DataType ParameterName ParameterSize
User::Code Input Int 0 -1
User::Supplier Input VarChar 1 -1
This would substitute the question marks in the SQL Statement property with the values contained in your variables.
Hope this helps,
Andy
|||Scott,
Any special reason for not using a dataflow with a lookup transform to detect if the rows exists(update) or not (insert). That is by far a pretty common practice in these scenarios.
|||Hi Rafael
Still new to this (and database stuff as a whole) and am going on someone elses advice!
I have looked at your suggestion and have got as far as the following:
OLEDB Source with a SQL select statement to return the data required
Look Up transform to look up the 2 columns from the Select against the destination table
After that I am a bit lost. I guess i have to add a OLEDB destination but do I do it to a table or a SQL Command?
thanks again
Scott
|||I think you are on the right track. I would add an OLE DB Destination against the destination table.
Keep in mind you have to tweak the lookup to 'redirect' errors. Lookup will treat the no matches as errors; hence will be send to the error output of the component (red arrow). Then you have to connect the error output of the Lup to the input of the destination.
Now the updates; every row going to the green output of the L.up is an existing/to-updated row. Here you have 2 options; use an OLE DB Commnad to update the row in the destination table; or send those rows to an estiging table (yes a seconf OLE DB Destination) and then back in control flow use an Execute SQl task to do a 1 time update. The advantage of the second method is performance. the Update runs 1 time updating all the required rows. The First one will perform an update for every row passing trhough; wich depending on the volume of data can be performance killer; the good thing is that you don't need a second table.
This thread has some examples
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1211340&SiteID=1
