OLE DB Source Adapter

The OLE DB source connection has several Access Modes:

• Openrowset
• Openrowset From Variable
• SQL Command
• SQL Command From Variable

For now, I am going to focus on the SQL Command options. Using the SQL Command Access Mode requires you to set the SqlCommand property (typing in your SQL query directly), effectively ‘hard coding’ the sql statement into the package. Using the SQL Command From Variable option allows you to set the SqlCommand property using a variable and subsequently by using an expression.

Data Reader Source

The Data Reader Source connection has only one Access Mode, and that is SQL Command. Don’t ask me why. At this level you can only set the SqlCommand property by typing in your query, or indeed, copy & paste.

Using an Expression to set the SqlCommand Property

“So then,” you ask, “how might I set the SqlCommand property for each of these Data Sources when it seems that I can’t?”. Here’s how. Let’s first concentrate on the OLE DB Source:

1. Create a new Variable of type string and set your SQL statement
2. Open up the OLE DB Source and select the ‘SQL Command from Variable’ option
3. Now, select the the variable created in step 1 as the variable that contains the SQL statement

At this point your OLE DB source is defined by the query that you have set in the Variable. We now need to create the expression that will define the query at runtime. We do this by navigating to the variable’s properties, setting the EvaluateAsExpression property to True and then configuring the expression in the Expression property.

Moving on to the Data Reader Source. With this adapter we only have the option of setting the SqlCommand directly. Or so I thought until recently. If you switch to the Control Flow design surface and select the Data Flow task that contains the Data Reader Source adapter, you will be able to set the SqlCommand using an expression.

1. Select the Data Flow task to bring up its properties
2. Click the ellipsis (…) to bring up the Expression Editor
3. Select the [DataReader Source].[SqlCommand] Property
4. Set your expression.

Using variables & expressions to set your queries enables you to centralise your queries, use configuration files to set database connections and capture the queries you are running in logging operations.  

Here’s a taster for what is available:

• A Whistle-stop tour of SSIS Add-ins
• Data Visualisation with Bing Maps for Enterprise
• Let’s make SQL Fly
• Microsoft SQL Server 2008 R2: What’s new in Reporting Services
• T-SQL Tuning with Colin Chapman, Enzo Ferrari, and The Stig

And of course the link to the entire list is right there under each of the presentation descriptions.

If you need a recap of SQLBits V you can read all about it here (Part 1) and here (Part 2).

Follow these easy steps:

1. Open SQL Server Management Studio,
2. Log on to the Reporting Services Instance that contains the reports you are looking for
3. Browser through the directory structure to the report that needs to be updated
4. Right-click the report and choose Edit…
5. Now follow the prompts to save the file to a destination of your choice
6. Open BIDS & create a new project/solution
7. Import the (previously) saved .rdl file into your SSRS project.
8. Edit away to your hearts content….

I’m not going to ask why you don’t have access to or have misplaced the files in the first place (No source code management? Seriously?). I am sure there are a myriad of reasons that you can come up with. This post merely provides a quick way to recover your files and continue edits/updates that may be required.