SSIS Catalog DB Dashboard
Hi,
This is not so much a Data Story but a template for a dashboard for looking at your own SSIS activity.
I use SSIS extensively with my job and over the years have used various tools to help me manage the packages and triage issues.
These include my own SSIS logs, the out of the box SSMS reports, Jamie Thompson's report pack and a number of SSIS catalog queries.
I had a quite good single query SSIS PowerBI Dashboard, but it was slow on large catalogs and limited in its use.
I started working on new dashboard that provided all of the features from all my past tools and around the time I saw a post from Chris Schmidt (link below) and so decided to use this as a starting point.
My dashboard is still not finished, but after lots of iterations I think it's going to be useful for others who need to monitor and understand what their SSIS packages are doing.
I first posted this a in 2017 and I've just given it an overhaul to support some of the new feature now supported by the August 2018 Desktop & Report server versions. Please give it a try and let me know if you spot any problems or things that could be improved.
I bring in and summarise the data is at a variety of levels
Execution (Execution & Execution Summary) The Package that is Executed First which I've named RootPackageName. This includes the Project & Folder
Package (Executable Package Stats) Package Summary. I group Packages by Types e.g. Master/Dimension/Fact/Stage/PostProcess. You can customised these in the PackageTypes Table. Click Advanced Editor to change it.
Executable (Executable Stats) Items inside the Package e.g. Tasks/Data Flows/Sequence. I also call this level Package Steps
I categorise packages and task into types using a keyword lookup. e.g. Package starting Fact for loading Fact tables.
The Task type names are based on common SSIS naming conventions.
This dashboard also provides details of any package errors and maps them to the Microsoft IS Error Reference Names.
Individual Executions can be viewed as a text based Gantt chart or as a matrix of executions by time slices.
Finally I extracted the Hierarchy from the execution paths to make a Network diagram and Sankey to visualise the structure and levels in an SSIS project.
Whilst developing this dashboard I managed to combine and try out a number PowerBI techniques such as;
Dax Measure to display a Gantt chart (Based on Chris Webb's Star Ratings)
Turn Package Paths into a Network diagram & Sankey Diagram
Scatter Chart to show hour and day matrix
Mini Gantt Timeline with Matrix
Mini Gantt Timeline with Scatter Chart
Dax Tables for Summary data
Vlookup function to use Package names to provide a type. This can do contains matches and use Start and End Indicators.
M Language tables for reference data
Parameterised SQL to Configure the Days to Load
Standard Deviation for tolerances.
Bookmarks & Selections
Report Tooltips
I've tried to keep the custom visuals to a minimum but I have used Sankey/Network Navigator as well as the OKViz Bullet and Sparklines.
The PowerBI is blank with that needs the server parameter setting to your SSIS db server before applying the changes and granting permissions.
The next network and rows can take a while to load wiht a large Catalog db so I have a small version that excludes these.
Templates and sample screen shots are available here https://github.com/stretcharm/SSIS-DB-Dashboard
Release Notes
v1.00
Improved query on Exectutions and Executables
Added Include fields for the Package types to configure the Master & Package Page filtering.
Edit PackageTypesUse Query to configure.
Changed Package filters
Add Date, Start, Execution ID Hierarchy to the Master and Package Pages
Added Preserve Layers Bookmark to help avoid window coming to the front
Remove Optional Job Server Code
Add Icon Ribbon and Help Page.
Minor Fixes
Thanks to the providers of the following pages that I've used to help in the making of this dashboard.
https://blogs.msdn.microsoft.com/sql_pfe_blog/2017/04/18/ssisdb-reporting-with-power-bi/
Chris Schmidt
https://www.excelguru.ca/blog/2015/01/28/creating-a-vlookup-function-in-power-query/
KenPuls
Star Ratings Quick Measure
http://community.powerbi.com/t5/Quick-Measures-Gallery/Star-Ratings/m-p/166903#M12
cwebb
https://ssisreportingpack.codeplex.com/
Jamie Thomson
Lots of Dax help and great OK Vis PowerBI Visualisations
http://www.sqlbi.com/
SSIS Catalog DB
https://docs.microsoft.com/en-us/sql/integration-services/service/ssis-catalog
Reza Rad's Article on the SSIS Catalog
http://www.rad.pasfu.com/index.php?/archives/75-SSIS-Catalog-Part-3-Folder-Hierarchy;-Folder,-Projects-and-Packages.html
DB Diagram
http://www.rad.pasfu.com/ssis/ssiscatalogpart3/5.png
SSIS Error Codes
https://docs.microsoft.com/en-us/sql/integration-services/integration-services-error-and-message-reference
Enjoy
Phil
Follow me on twitter https://twitter.com/StretchArm1 for updates
Other gallery entries
PowerBI/SQL Server and Microsoft Business Application Related YouTube Videos
https://community.powerbi.com/t5/Data-Stories-Gallery/PowerBI-SQL-Server-and-Microsoft-Business-Application-Related/m-p/743806#M2779)
SQL Saturday Sessions https://community.powerbi.com/t5/Data-Stories-Gallery/Pass-SQLSaturday-Dashboard/m-p/489529#M2153
Microsoft Bus App Summit & SQL Bits videos
and PowerBI Custom Visual
https://community.powerbi.com/t5/Data-Stories-Gallery/PowerBI-Custom-Visuals/td-p/724185
Most code is also here https://github.com/stretcharm
eyJrIjoiZDM0N2NmMjMtZmE2NS00MDE1LWJkOWQtZmFmZmZkMzI4ZDBkIiwidCI6ImEwYTcyYzIzLTdlMWEtNGYxOC05NDU4LTlhNzUyYTEzMTg1NCJ9
58 Replies
- stretcharm
Memorable Member
Just noticed that changing servers can cause the Execution to Date Join to be dropped.
Just add it back from ExecutionStartDate to Date
- stretcharm
Memorable Member
Updated version 0.77 templates (blank docs as I cannot upload templates)
Changed to use Ribbon charts
Fixed Gantt Calculation
Added Some DrillthroughsFixed Date join issue
Improved query performance on large SSIS DBsSmall template doesn't include the rows or network diagrams that can be slow.
I've also added a post in the Quick Measures for the Text Gantt Dax
http://community.powerbi.com/t5/Quick-Measures-Gallery/Text-Gantt-Chart/m-p/253466
- stretcharm
Memorable Member
Updated version 0.78 templates (blank docs as I cannot upload templates).
Use the Server Name Parameter and Apply. Then do a refresh. If you want the Rows manually Refresh Execution Stats Rows as it's not included in the refresh.
Changes.
Added Percentage completion estimates to the Currently Running Tab
Improved query performance on large SSIS DBs
Execution Stats has commented out the time filter as its quicker on my server. If you have a large ssisdb you may want to uncomment.
Improved query for Execution Hierarchy and it's now included in the Refereses
Improved query for Execution Stats Rows. Still not not included in the refresh as it can be slow, but you can refresh manually.
Add a Execution Comparison tab
Add a Execution Over Time tab using scatter play axisHere are some new screen shots
ExecutionOverTimeExecutionComparisonExecutionGanttExecutionStepsPackagesMaster PackagesExecutionListSummarySummaryExecutionPerformance
- jprinceNew MemberHello,
This is an amazing job you have done. We are in the process of selecting an ETL and I am afraid of the black box effect of SSIS. This is a way to mitigate. Do you think it could work at field level to do data lineage?
The answer is probably no as it would require to parse each package code, but we never know :)
Thanks- stretcharm
Memorable Member
Yes it can be tricky to get the full lineage of SSIS. The SSISDB Catalog doesn't hold this level of data, but it's there in the pacakge xml.
Probably the ideal solution is to use metadata and build packages using BIML. This way your lineage design builds the package so you get documentation and generate the code. BIML is not going to work with complex SSIS requirements though.
Doc Xpress does a decent job of extracting the SSIS guts for documentation. It has lineage functions, but this not as useful as it sounds.
http://help.sentryone.com/docxpress/Index.html?SSISPackage.html
https://www.sentryone.com/products/pragmatic-workbench/doc-xpress/sql-metadata-management
You can also extract code from SSIS using powershell
We are moving to a metadata management of package and source dependancies. Eventually we may add column level lineage, but for now we are doing it on a table/data set level. This will allow us to see which target areas are impacted by any source system issues.
- rshinaRegular Visitor
This looks like a great way to monitor jobs, thanks for posting. I have downloaded the "SSISDB_Dashboard_v0_81_Full_Blank.pbix" version and can change the msdn connection from localhost to the sql instance that we are looking to monitor. However I cannot find a way to modify the SSISDB connection. The Edit Connection button greys out when I select it.
Any assistance would be greatly appreciated.
Thanks
- stretcharm
Memorable Member
Change the ServerName Parameter.
This is used for all connections.
Apply should then repoint everything to your server. You should not need to change the SSISdb unless is got a different db name.
Alternativly get the template version from this path as they prompt you to enter the parameters when you open them.
https://github.com/stretcharm/SSIS-DB-Dashboard
If you get errors after changing the refresh each query manully in the query editor to ensure it's happy. Sometimes if needs help to get going. Also note that v81 doesn't like it if you have not executions so make sure you've got something in your SSISDB.
- jdrazkowskiNew Member
This has been a very helpful dashboard. How would you interpret the scatterchart on the 'Execution Gantt' page with StartOrderRev on the y-axis and Step Order End on the x-axis?
- stretcharm
Memorable Member
It's showing the Package Durations and Start time/End Times in slices of 15 minutes. So it's a bit like a visual gantt.
The start is reversed so the scatter flows downwards over time.
Below is a sample that shows -6 = 6am to -10 =10am and on the x axis 6.5 = 6:30am and 9.5= 9:30am
Size of the bubbles are durations.
You can click the bubbles to filter the gantt or hover to see details.
- dooncomputerFrequent Visitor
I would be nice to have option to enter diffferent server name for MSDB and SSISDB?
- dooncomputerFrequent Visitor
I would be nice to have option to enter diffferent server name for MSDB and SSISDB?
- stretcharm
Memorable Member
The database and server are both parameters so you can set them to anything, however they are currently the same server.
You can adjust your version to add yourself a new server param for your msdb query in the query editor.
I'll add the MSDB and Job Server as new params in the next version. I'll also add an option to disable this as I don't always have access to the job details.
- stretcharm
Memorable Member
Big new version so I've updated the screens and doing a full description again.
I use SSIS extensively with my job and over the years have used various tools to help me manage the packages and triage issues.
These include my own SSIS logs, the out of the box SSMS reports, Jamie Thompson's report pack and a number of SSIS catalog queries.
I had a quite good single query SSIS PowerBI Dashboard, but it was slow on large catalogs and limited in its use.
I started working on new dashboard that provided all of the features from all my past tools and around the time I saw a post from Chris Schmidt (link below) and so decided to use this as a starting point.
My dashboard is still not finished, but after lots of iterations I think it's going to be useful for others who need to monitor and understand what their SSIS packages are doing.I first posted this a in 2017 and I've just given it an overhaul to support some of the new feature now supported by the August 2018 Desktop & Report server versions. Please give it a try and let me know if you spot any problems or things that could be improved.
I bring in and summarise the data is at a variety of levels
Execution (Execution & Execution Summary) The Package that is Executed First which I've named RootPackageName. This includes the Project & Folder
Package (Executable Package Stats) Package Summary. I group Packages by Types e.g. Master/Dimension/Fact/Stage/PostProcess. You can customised these in the PackageTypes Table. Click Advanced Editor to change it.
Executable (Executable Stats) Items inside the Package e.g. Tasks/Data Flows/Sequence. I also call this level Package Steps
I categorise packages and task into types using a keyword lookup. e.g. Package starting Fact for loading Fact tables.The Task type names are based on common SSIS naming conventions.
This dashboard also provides details of any package errors and maps them to the Microsoft IS Error Reference Names.
Individual Executions can be viewed as a text based Gantt chart or as a matrix of executions by time slices.
Finally I extracted the Hierarchy from the execution paths to make a Network diagram and Sankey to visualise the structure and levels in an SSIS project.
Whilst developing this dashboard I managed to combine and try out a number PowerBI techniques such as;Dax Measure to display a Gantt chart (Based on Chris Webb's Star Ratings)
Turn Package Paths into a Network diagram & Sankey Diagram
Scatter Chart to show hour and day matrix
Mini Gantt Timeline with Matrix
Mini Gantt Timeline with Scatter Chart
Dax Tables for Summary data
Vlookup function to use Package names to provide a type. This can do contains matches and use Start and End Indicators.
M Language tables for reference data
Parameterised SQL to Configure the Days to Load
Standard Deviation for tolerances.Bookmarks & Selections
Report Tooltips
I've tried to keep the custom visuals to a minimum but I have used Sankey/Network Navigator as well as the OKViz Bullet and Sparklines.
The PowerBI is blank with that needs the server parameter setting to your SSIS db server before applying the changes and granting permissions.Templates and sample screen shots are available here https://github.com/stretcharm/SSIS-DB-Dashboard
Release Notes
v1.00
New Layout with Filter and Help Screens and Visualisation Toggles
Conditional Formating on Execution List
Add Execution Step Gantt and Project/Package Parameters
Report Tooltip on Gantt
Fix Duration if Package is called twice in an Execution
Add Option for different Server for SQL Jobs
Add TaskType Lookup based on naming convention
Add support for ^(start) and $(end) in Package Name and Task Type Lookups
Thanks to the providers of the following pages that I've used to help in the making of this dashboard.
https://blogs.msdn.microsoft.com/sql_pfe_blog/2017/04/18/ssisdb-reporting-with-power-bi/
Chris Schmidt
https://www.excelguru.ca/blog/2015/01/28/creating-a-vlookup-function-in-power-query/
KenPuls
Star Ratings Quick Measure
http://community.powerbi.com/t5/Quick-Measures-Gallery/Star-Ratings/m-p/166903#M12cwebb
https://ssisreportingpack.codeplex.com/
Jamie Thomson
Lots of Dax help and great OK Vis PowerBI Visualisations
http://www.sqlbi.com/
SSIS Catalog DB
https://docs.microsoft.com/en-us/sql/integration-services/service/ssis-catalog
Reza Rad's Article on the SSIS Catalog
http://www.rad.pasfu.com/index.php?/archives/75-SSIS-Catalog-Part-3-Folder-Hierarchy;-Folder,-Projects-and-Packages.html
DB Diagram
http://www.rad.pasfu.com/ssis/ssiscatalogpart3/5.png
SSIS Error Codes
https://docs.microsoft.com/en-us/sql/integration-services/integration-services-error-and-message-referenceEnjoy
Phil
- AnonymousNot applicable
Is there a trick to getting the dataset to refresh on a schedule when the report is published to PowerBI?
I get an error that the dataset has one or more sources that don't support refresh. Clicking discover data sources gives me the response "Query contains unknown or unsupported data sources".
I love the report though. I jsut wantto be able to share it with the entire team in main site for viewing diagnostics on our various servers.
Thanks,
Phil
- stretcharm
Memorable Member
In order to get the powerbi service working you'll need to use the Gateway to connect to your servers (unless they are in azure )
https://powerbi.microsoft.com/en-us/gateway/
You'll need pro licences to share and use the gateway.
I share the report via the team on premise using the PowerbI Report Server (SSRS + PowerBI) can be added to existing sql servers you have enterprise and maintainance. Just need a powerbi pro licence to upload reports.
https://powerbi.microsoft.com/en-us/report-server/
Both of these would then let you set a schedule.
- hariannem93New Member
Hi stretcharm
Can you please share SQL code for Executions, Failed Executions, Package Steps, and Error Codes?
stretcharm wrote:
Hi,
This is not so much a Data Story but a template for a dashboard for looking at your own SSIS activity.
I use SSIS extensively with my job and over the years have used various tools to help me manage the packages and triage issues.
These include my own SSIS logs, the out of the box SSMS reports, Jamie Thompson's report pack and a number of SSIS catalog queries.
I had a quite good single query SSIS PowerBI Dashboard, but it was slow on large catalogs and limited in its use.
I started working on new dashboard that provided all of the features from all my past tools and around the time I saw a post from Chris Schmidt (link below) and so decided to use this as a starting point.
My dashboard is still not finished, but after lots of iterations I think it's going to be useful for others who need to monitor and understand what their SSIS packages are doing.I first posted this a in 2017 and I've just given it an overhaul to support some of the new feature now supported by the August 2018 Desktop & Report server versions. Please give it a try and let me know if you spot any problems or things that could be improved.
I bring in and summarise the data is at a variety of levels
Execution (Execution & Execution Summary) The Package that is Executed First which I've named RootPackageName. This includes the Project & Folder
Package (Executable Package Stats) Package Summary. I group Packages by Types e.g. Master/Dimension/Fact/Stage/PostProcess. You can customised these in the PackageTypes Table. Click Advanced Editor to change it.
Executable (Executable Stats) Items inside the Package e.g. Tasks/Data Flows/Sequence. I also call this level Package Steps
I categorise packages and task into types using a keyword lookup. e.g. Package starting Fact for loading Fact tables.The Task type names are based on common SSIS naming conventions.
This dashboard also provides details of any package errors and maps them to the Microsoft IS Error Reference Names.
Individual Executions can be viewed as a text based Gantt chart or as a matrix of executions by time slices.
Finally I extracted the Hierarchy from the execution paths to make a Network diagram and Sankey to visualise the structure and levels in an SSIS project.
Whilst developing this dashboard I managed to combine and try out a number PowerBI techniques such as;Dax Measure to display a Gantt chart (Based on Chris Webb's Star Ratings)
Turn Package Paths into a Network diagram & Sankey Diagram
Scatter Chart to show hour and day matrix
Mini Gantt Timeline with Matrix
Mini Gantt Timeline with Scatter Chart
Dax Tables for Summary data
Vlookup function to use Package names to provide a type. This can do contains matches and use Start and End Indicators.
M Language tables for reference data
Parameterised SQL to Configure the Days to Load
Standard Deviation for tolerances.Bookmarks & Selections
Report Tooltips
I've tried to keep the custom visuals to a minimum but I have used Sankey/Network Navigator as well as the OKViz Bullet and Sparklines.
The PowerBI is blank with that needs the server parameter setting to your SSIS db server before applying the changes and granting permissions.The next network and rows can take a while to load wiht a large Catalog db so I have a small version that excludes these.
Templates and sample screen shots are available here https://github.com/stretcharm/SSIS-DB-Dashboard
Release Notes
v1.00Improved query on Exectutions and Executables
Added Include fields for the Package types to configure the Master & Package Page filtering.
Edit PackageTypesUse Query to configure.Changed Package filters
Add Date, Start, Execution ID Hierarchy to the Master and Package Pages
Added Preserve Layers Bookmark to help avoid window coming to the front
Remove Optional Job Server Code
Add Icon Ribbon and Help Page.
Minor Fixes
Thanks to the providers of the following pages that I've used to help in the making of this dashboard.
https://blogs.msdn.microsoft.com/sql_pfe_blog/2017/04/18/ssisdb-reporting-with-power-bi/
Chris Schmidt
https://www.excelguru.ca/blog/2015/01/28/creating-a-vlookup-function-in-power-query/
KenPuls
Star Ratings Quick Measure
http://community.powerbi.com/t5/Quick-Measures-Gallery/Star-Ratings/m-p/166903#M12cwebb
https://ssisreportingpack.codeplex.com/
Jamie Thomson
Lots of Dax help and great OK Vis PowerBI Visualisations
http://www.sqlbi.com/
SSIS Catalog DB
https://docs.microsoft.com/en-us/sql/integration-services/service/ssis-catalog
Reza Rad's Article on the SSIS Catalog
http://www.rad.pasfu.com/index.php?/archives/75-SSIS-Catalog-Part-3-Folder-Hierarchy;-Folder,-Projects-and-Packages.html
DB Diagram
http://www.rad.pasfu.com/ssis/ssiscatalogpart3/5.png
SSIS Error Codes
https://docs.microsoft.com/en-us/sql/integration-services/integration-services-error-and-message-referenceEnjoy
Phil
eyJrIjoiYmY4NTM4NWUtM2RjMS00YmVhLWI1ODAtOTM1NzZmNDgyMzVlIiwidCI6IjIxYjJlNDJkLTBkZWYtNGUxZC04OWY1LTEyZmMwZTJhZmQwNCIsImMiOjh9
stretcharm wrote:
Hi,
This is not so much a Data Story but a template for a dashboard for looking at your own SSIS activity.
I use SSIS extensively with my job and over the years have used various tools to help me manage the packages and triage issues.
These include my own SSIS logs, the out of the box SSMS reports, Jamie Thompson's report pack and a number of SSIS catalog queries.
I had a quite good single query SSIS PowerBI Dashboard, but it was slow on large catalogs and limited in its use.
I started working on new dashboard that provided all of the features from all my past tools and around the time I saw a post from Chris Schmidt (link below) and so decided to use this as a starting point.
My dashboard is still not finished, but after lots of iterations I think it's going to be useful for others who need to monitor and understand what their SSIS packages are doing.I first posted this a in 2017 and I've just given it an overhaul to support some of the new feature now supported by the August 2018 Desktop & Report server versions. Please give it a try and let me know if you spot any problems or things that could be improved.
I bring in and summarise the data is at a variety of levels
Execution (Execution & Execution Summary) The Package that is Executed First which I've named RootPackageName. This includes the Project & Folder
Package (Executable Package Stats) Package Summary. I group Packages by Types e.g. Master/Dimension/Fact/Stage/PostProcess. You can customised these in the PackageTypes Table. Click Advanced Editor to change it.
Executable (Executable Stats) Items inside the Package e.g. Tasks/Data Flows/Sequence. I also call this level Package Steps
I categorise packages and task into types using a keyword lookup. e.g. Package starting Fact for loading Fact tables.The Task type names are based on common SSIS naming conventions.
This dashboard also provides details of any package errors and maps them to the Microsoft IS Error Reference Names.
Individual Executions can be viewed as a text based Gantt chart or as a matrix of executions by time slices.
Finally I extracted the Hierarchy from the execution paths to make a Network diagram and Sankey to visualise the structure and levels in an SSIS project.
Whilst developing this dashboard I managed to combine and try out a number PowerBI techniques such as;Dax Measure to display a Gantt chart (Based on Chris Webb's Star Ratings)
Turn Package Paths into a Network diagram & Sankey Diagram
Scatter Chart to show hour and day matrix
Mini Gantt Timeline with Matrix
Mini Gantt Timeline with Scatter Chart
Dax Tables for Summary data
Vlookup function to use Package names to provide a type. This can do contains matches and use Start and End Indicators.
M Language tables for reference data
Parameterised SQL to Configure the Days to Load
Standard Deviation for tolerances.Bookmarks & Selections
Report Tooltips
I've tried to keep the custom visuals to a minimum but I have used Sankey/Network Navigator as well as the OKViz Bullet and Sparklines.
The PowerBI is blank with that needs the server parameter setting to your SSIS db server before applying the changes and granting permissions.The next network and rows can take a while to load wiht a large Catalog db so I have a small version that excludes these.
Templates and sample screen shots are available here https://github.com/stretcharm/SSIS-DB-Dashboard
Release Notes
v1.00Improved query on Exectutions and Executables
Added Include fields for the Package types to configure the Master & Package Page filtering.
Edit PackageTypesUse Query to configure.Changed Package filters
Add Date, Start, Execution ID Hierarchy to the Master and Package Pages
Added Preserve Layers Bookmark to help avoid window coming to the front
Remove Optional Job Server Code
Add Icon Ribbon and Help Page.
Minor Fixes
Thanks to the providers of the following pages that I've used to help in the making of this dashboard.
https://blogs.msdn.microsoft.com/sql_pfe_blog/2017/04/18/ssisdb-reporting-with-power-bi/
Chris Schmidt
https://www.excelguru.ca/blog/2015/01/28/creating-a-vlookup-function-in-power-query/
KenPuls
Star Ratings Quick Measure
http://community.powerbi.com/t5/Quick-Measures-Gallery/Star-Ratings/m-p/166903#M12cwebb
https://ssisreportingpack.codeplex.com/
Jamie Thomson
Lots of Dax help and great OK Vis PowerBI Visualisations
http://www.sqlbi.com/
SSIS Catalog DB
https://docs.microsoft.com/en-us/sql/integration-services/service/ssis-catalog
Reza Rad's Article on the SSIS Catalog
http://www.rad.pasfu.com/index.php?/archives/75-SSIS-Catalog-Part-3-Folder-Hierarchy;-Folder,-Projects-and-Packages.html
DB Diagram
http://www.rad.pasfu.com/ssis/ssiscatalogpart3/5.png
SSIS Error Codes
https://docs.microsoft.com/en-us/sql/integration-services/integration-services-error-and-message-referenceEnjoy
Phil
eyJrIjoiYmY4NTM4NWUtM2RjMS00YmVhLWI1ODAtOTM1NzZmNDgyMzVlIiwidCI6IjIxYjJlNDJkLTBkZWYtNGUxZC04OWY1LTEyZmMwZTJhZmQwNCIsImMiOjh9 - MednaxKevinFrequent Visitor
Is there any way to merge multiple SSIS servers into a single dashboard? We have quite a few SSIS servers and having a dashboard for each seems a bit "much".- stretcharm
Memorable Member
MednaxKevin wrote:
Is there any way to merge multiple SSIS servers into a single dashboard? We have quite a few SSIS servers and having a dashboard for each seems a bit "much".I run on different environments and prefer to have different dashboards. Mainly for performances and clarity reasons.
The dashboard could be altered to combine multiple servers.
If you could take the code from github and you cab duplicate source queries and merge the results.
add some more Parameters for the other servers
Follow this process for each query
Duplicate Query 1 e.g Packages to PackagesServer1 to PackagesServerX
Change the parameters to the correct server
on one Query use Append Queries as New to create AllPackageServers and include each of the PackagesServer queries
Get the Code (Advanced Editor) from AllPackageServers and paste over the original Packages Query code
You can discard AllPackageServers and uncheck enable load for each for the PackageServer Queries (unless you need to debug their results)
Powerbi will now use the combined results instead of the single server version
The biggest issue you'll have will be with any duplicates from the different servers. Any Number based keys such as PackageID and ExecutionID could duplicate. You may need to add a server prefix to anything that has a problem.
I would definitely add a server code to the Project or Folder Name so that you can see the source server
The other option would be to use SSIS to collate all the data into a set of tables (based on the current queries) and then update the dashboard queries to use these. You could control and manage issues like duplicate keys as you load the data. This would definitely give better performance, but you'd have to update the tables before the dashboard.