These posts are about Biml (Business Intelligence Markup Language), BimlScript, BimlExpress, BimlStudio, BimlOnline, the BimlHero Certified Expert Program and events by the Biml community or Varigence. Older posts may mention BI Developer Extensions, BIDS Helper and Mist.
Biml objects have many built-in attributes. For example, all Tables have SchemaName and all Packages have ProtectionLevel. When your Biml solution starts to grow, you will quickly see the need for adding additional metadata that can be used in other Biml files. A common use case in Data Warehouse Staging projects is to store the source schema and source table name on your staging table objects. This allows you to use the source metadata in a higher tier Biml file that generates the SSIS packages to load the tables. To store and use this additional metadata, you can use Biml Annotations or ObjectTags.
Biml Annotations and ObjectTags are both Key/Value pairs. Annotations are String/String pairs intended for storing simple text metadata, while ObjectTags are String/Object pairs that can also store more complex metadata in .NET objects.
Many Biml solutions start off very simple, with just a single Biml file that generates a few SSIS packages. Most developers quickly see the need for a more complex solution for multiple sources. One way to reuse code and apply the Don’t Repeat Yourself software engineering principle in Biml is to use Tiered Biml Files.
In addition to using Tiered Biml Files, there are four other main ways you can avoid repeating your Biml code:
Woohoo! The Biml Book: Business Intelligence and Data Warehouse Automation is now available for pre-order from Amazon and Apress! :D
This is the first book I’ve co-authored, and I have to admit it’s a very strange feeling to see my name on the cover of a book. Am I allowed to say I’m quite proud? Oh, I’ll say it anyway. I’m proud and very honored to have written this book with such a talented group of people: Andy Leonard (@AndyLeonard), Scott Currie (@scottcurrie), Ben Weissman (@bweissman), Bill Fellows (@billinkc), Martin Andersson (@frysdisken), Peter Avenant (@PeterAvenant), Simon Peck (@biguynz), Reeves Smith (@SQLReeves), Raymond Sondak (@raymondsondak) and Jacob Alley.
What’s in The Biml Book?
The first part of the book starts with the basics: getting your development environment configured, Biml syntax, and scripting essentials.
The next part of the book guides you through the process of using Biml to build a framework that captures both your design patterns and execution management. In addition to leveraging design patterns in your framework, you will learn how to build a robust metadata store and how to package your framework into Biml bundles for deployment within your enterprise.
In the last part of the book, you will learn more advanced Biml features and capabilities, such as SSAS development, T-SQL recipes, automated documentation, and Biml troubleshooting.
When can I get The Biml Book?
Amazon says early December, but it might be available sooner. If you don’t want to wait, you can pre-order The Biml Book from Amazon or Apress right now.
Yay! This has been a long journey, and I’m so happy the other guys let me be a part of it :)
Are you tired of right-clicking on your Biml files to Check Biml for Errors or to Generate SSIS Packages? Did you know that you can create your own BimlExpress Keyboard Shortcuts? :)
Go to Tools → Options:
Select Environment → Keyboard, then type Biml in the Show commands containing box:
Select a Biml command, click in the Press shortcut keys box, click the keyboard shortcut combination of your choice, and click the Assign button. In this example, I have used Ctrl+Shift+C, Ctrl+Shift+B (I chose C then B for “Check Biml”):
Click OK, and that’s it! You can now use your keyboard shortcuts while having one or more Biml files selected. The shortcuts will appear in your BimlExpress menus in the toolbar and when you right-click on a file :)