Now that we’ve deployed what I like to call the backend of our BI solution, lets look at how to deploy our PowerBI reports. For various reasons, we are not using PowerBI.com but PowerBI Report Server hosted by another team in our group, shared amongst companies.
Now that we have an artifact that we can deploy, lets push it onto our target environments. In this first article I will cover how we do it for DBs, SSIS, SSAS and why we do it. I’ll cover PowerBI in a later article as there is no task available for the On Premise version of PowerBI Report Server that we use and we had to rely on a custom script.
Now that we store our glorious code in Git and make sure some poor trainee will be able to go over it in 10 years (and maybe even understand it if we do end up documenting it fully one day), getting down to actually delivering it will help us justify our salaries better.
Everybody in IT uses source control. There is no more debating why. We’ve all struggled without it for long enough.
For us, it has become the root of our work. If it isn’t in source control, it doesn’t exist. But how do we go about it?
Over the next five blog posts, I’ll be going into the details of why and how my team has reached the level of maturity and control over its BI development process that it has.
Having passed the 10-year experience mark working with Information Systems, I felt it was time to share some insight people might find useful.