In exactly one month from now, on September 1st, I will be speaking at SQLSaturday Oslo 2018! This year is a small milestone for us, as it is our fifth SQLSaturday in Oslo. Woohoo!
SQLSaturday Oslo 2018 Schedule
I will be presenting… Actually, hang on! I will get back to that in a bit. Scroll down for some rambling about my session :) But first, the important stuff:
There are 30 sessions by 27 speakers from 11 countries scheduled this year.
Of the 27 speakers, there are 7 women, and 4 of the women are Norwegian! These are amazing numbers for an event like this. I am SO proud and SO happy :D Thank you to the organizers for encouraging and supporting women in tech, and a huge thank you to these amazing women for being great role models: Dagrun Haugland, Gabi Münster, Ida Bergum, Kathi Kellenberger, Sara Jønvik, and Steph Locke.
Same topic, same basic concept and ideas, some similar visualizations, but a very different session. And I mean in more ways than going from 4:3 to 16:9:
I have changed
My hair is much longer and my URL is much shorter. I’ve become a BimlHero and Data Platform MVP, and I’ve co-authored two Biml books. And it all started with this one Biml session back in 2014! Crazy :)
Do you have large Visual Studio solutions with many projects? Are you looking for an easy way to hide some projects while working on others? Maybe you are a fellow speaker looking for a way to group and organize your demo files? Solution Folders may be what you are looking for!
What are Visual Studio Solution Folders?
In Visual Studio, you can add virtual folders to group and organize your projects and files. Folders can be nested, collapsed, expanded, and even hidden in the Solution Explorer. Please keep in mind that these folders are entirely virtual. That means that you will still have to physically organize your projects the way you prefer in your file system.
Create Solution Folders
Right-click on the solution → Add → New Solution Folder (or with the solution selected, click the Project menu → Add New Solution Folder)
Hide Solution Folders
Right-click on the folder → Hide Folder (or with the folder selected, click the Project menu → Hide Folder)
Show Solution Folders
Right-click on the solution → Unhide Folders (or with the solution selected, click the Project menu → Unhide Folders)
As of July 2018, there is no built-in Biml support for OData. To work with OData in Biml, you have to create a custom source and connection manager. This requires more Biml code than built-in functions like OleDbSource and may look a little overwhelming at first. But don’t worry! You don’t have to start from scratch.
In this blog post, we will first look at the properties of the OData Connection Manager and how to script it in Biml. Then, we will do the same for the OData Source. Finally, we will tie it all together and create a complete SSIS package that you can use a starting point for your own projects.
The Quick and Easy Solution
But before we dig into any code, let’s skip to the quick, easy, and timesaving solution. That’s what we all really want, right? :)
Create an example SSIS package using an OData Source and Connection Manager
Convert the SSIS package to Biml
As promised: quick, easy, and timesaving! The new Convert SSIS Packages to Biml feature was released in BimlExpress 2018, and it really is a lifesaver. After converting to Biml, you can simply copy and paste the code into your projects.
You may run into some bugs when you convert your SSIS packages to Biml. I ran into two issues while writing this blog post. The first was that I had to add UsesDispositions=”true” to the Source component. The second was that the data types in the Source component were prefixed with System. I have fixed both of these issues in my examples below. In addition to these issues, the converted Biml also contained some unnecessary code. Unnecessary code does not break anything, but it can make your code harder to read and maintain. Personally, I prefer my code to be as clean and simple as possible.