<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=931099456970389&amp;ev=PageView&amp;noscript=1">


As a developer, do you often find yourself frustrated with tasks that should be easier to complete? There are many different aspects of the developer role that can be tedious and drawn out. That's why we created BI xPress to simplify your experience when working inside SSDT. Let’s take a look at some common practices in a BI environment and how BI xPress makes those practices easier and smoother to implement.

Package Auditing

When SSIS packages fail, the cause of the failure can often take a significant amount of time to diagnose. Typically, developers will need to dig through SSIS error messages, and sometimes it can be difficult to make sense of those errors. Creating some sort of an auditing framework within an SSIS package will help make this process easier. A good framework will capture as much execution data as possible. This can be logged to a SQL Server database and can be reported on, ideally. To do this manually can be a time consuming task. The standard framework would consist of tasks being added to event handlers and row counts for sources and destinations in each dataflow task. Plus, the more developers that are working on packages, the higher the chances that some will deviate from the standard.

How does BI xPress help with this? BI xPress contains its own auditing framework feature that developers can use to apply the same framework to each package in a matter of seconds. Using the BI xPress Auditing Framework Wizard, developers can choose where the execution data will be stored and select exactly what will be logged. This will save hours on development time and easily implement a standard.


Package Monitoring

When logging execution data, it would only make sense to report against that data. This is another process that can be time consuming. First, the team needs to identify what metrics they are interested in seeing in the reports.

BI xPress comes with a collection of static reports that will display detailed information about many aspects of the package executions. The reports will display general execution data, extract and load trends, and package alerts, just to name a few. Most importantly, there is the Monitoring Console. This report displays real-time package monitoring during execution. It gives a visual of the package, just like what would be seen when running a package in SSDT. This report cuts down on the amount of time spent troubleshooting package errors.


Click to Tweet: 3 Ways BI xPress makes a DBA's job easier http://bit.ly/2bcs6SF

Rapid Package Development

At some point, you could find yourself in a situation where you need to recreate packages you have already built or create similar packages. While the package could be copied, you would have to remember to reset package ID’s and adjust all the required properties to get the package to run in against different connections or data sets. This can take time, and in some cases, a little bit of trial and error.

The Package Builder feature in BI xPress reduces the amount of time spent on creating these redundant packages by using a system of templates. You can create a template of a package and during the creation you can highlight properties that would need to be changed in order to use it in a different environment. Then the template can be used with the Package Builder Wizard to recreate the package in a matter of seconds.


These are just a few of the features that can simplify a developer’s everyday tasks. Want to find out first hand how BI xPress can simplify your job? Try it free for 14 days: 

Try BI xPress


Join Our Blog

Join thousands of other SQL Server, BI and cloud pros by subscribing to our blog.

Leave a comment

Posts by Topic

see all

Recent Articles

Popular Articles