Are you using Biml so you won’t have to do the same tasks over and over and over again in multiple SSIS packages? If so, you probably don’t want to write the same Biml code over and over and over again either. Instead, you can move common code to separate files, centralize and reuse these files in many projects, and update code in one file to make changes to all projects. One of the ways to apply this Don’t Repeat Yourself software engineering principle in Biml is to use CallBimlScript.
In addition to using CallBimlScript, there are four other main ways you can avoid repeating your Biml code:
If the regular sessions aren’t enough learning for you, register for one of the pre-cons on the April 24th training day:
SQL Server: An Introduction – William Durkin (@sql_williamd)
Understanding SSIS internals and performance tuning – David Peter Hansen (@DPHansen)
R: from analysis to integration – Steph Locke (@SteffLocke)
Optimising Reporting Services for MDX Data Sources – Bob Duffy (@bob_duffy)
Performance Troubleshooting for the (Accidental) DBA – Mark Pryce-Maher (@MarkPM_MSFT) / Richard Douglas (@SQLRich)
Yesterday we did another fun #SQLHangout about Biml. This time we were joined by João Lopes (@SQLSniper), Rasmus Reinholdt (@RasmusReinholdt) and Régis Baccaro (@regbac) – great guys that I admire. It was interesting to hear how we use Biml in different ways and what we would like to see happen in 2015. I look forward to seeing all of them again and learn from their experiences!
BIML in the real world. v2!
Five people from Bulgaria, Denmark, Portugal and Norway talking about Biml – isn’t that awesome? :)