In SQL Server Integration Services, you can specify that an OLE DB Connection use a SQL Statement from a variable.
Using this approach, you can dynamically build SQL statements using the OLE DB Connection. But what about ADO.NET?
It appears we have no way to dynamically build SQL statements when using ADO.Net providers. And to think I’ve been standardizing on them. On the other hand, maybe we do have a way. I made a package with two variables. One is a DateTime called LoadControl and the other is a string called strSQL. I’m going to load a DateTime from a load control table into the LoadControl variable then use the LoadControl variable to build the WHERE clause of a SQL statement to pull out all medical claims with a date of service greater than or equal to the LoadControl date. First, our variables.
Nothing hard about that. Next, our Execute SQL task to populate the LoadControl variable.
Next up, our data flow.
The only thing I’ve done is set up the ADO.Net Source. Now we need to get our strSQL variable populated. First, be certain to set the property EvaluateAsExpression to TRUE for strSQL.
Next, create an expression for this variable like so. Notice that since DateTime variables cannot be NULL when you create them, SSIS fills in the current DateTime, hence the 5/3/2015 7:38:04 PM.
Now the interesting part. From the Control Flow, single-left click your data flow to highlight it. Now, look over at your Properties for your data flow. Scroll down to the Misc. section.
That’s right, you see the SQL statement for the ADO.Net source. Of course, this is where it is important to call your connection sources something meaningful so you can find them readily (I didn’t bother since we only have one). Notice that we have two spots for the ADO.Net source: SQL Command and TableOrViewName. We aren’t going to change the SQL statement there. Rather, go down further until you see Expressions. That’s right, build an expression.
Notice that for this expression, we only need the strSQL variable. Once you have that saved, put a data viewer on your package and run it.
Notice that only dates for 4/10/2015 or higher are shown (I added an Order By to the SQL Statement in strSQL and 4/10/2015 is what was in our LoadControl Table). This is where our Expression was evaluated and placed in for the SQL Command of the ADO.Net source. One thing of note, notice how before I set up a SQL statement in the ADO.NET Connection when I first created it earlier. This statement is IGNORED when the Expression is evaluated. However, if the SQL Statement in your Expression adds or changes columns, you may need to go into the Advanced Editor of the ADO.NET Connection and click Refresh to get those changes to show. Otherwise, your new or changed columns may not show up in the data flow right away.
With this approach, you can still dynamically build SQL statements for ADO.NET Connections like you can OLE DB Connections. A little more work, yes, but I think worth it when you have lots of Script Tasks/Components that need to use Connection Managers.
2 thoughts on “SSIS: Using Expressions to build SQL Statements for ADO.NET Connections”
How can I use this to do an update statement on an ADO.net destination connection?
Set Lookupcode = @[User::LookupCode]
Where ItemNo = @[User::ItemNo]
Thanks for writing. To do an update statement you have three main choices: The OLEDB command which, as the name implies, is OLEDB only so will not work in this case. The Execute SQL Statement which isn’t even in the data flow so that’s a no go, as well. Or, use a Script Component. For most of us, the Script Component would be the way to execute an update statement using an ADO.NET connection.
As a third-part solution, the good folks at Cozy Roc have an ADO.NET Command that you can use. http://www.cozyroc.com/script/adonet-command-transformation