You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a great project, and it is exactly what I was looking to build myself. One suggestion, though, is that it would be much more useful if it wasn't dependent on (or expecting) Azure SQL. While the data collection script works with a local db, the report template does not. Since I am a complete novice with Power BI, it took a while to figure out why. With the port number hard coded in the queries, it prevents Power BI Desktop from connecting to a local SQL Server DB on the same machine. Once I modified all of the queries to remove the port number, the report ran like a champ.
I would suggest removing the port number from all queries and specifying that it needs to be included with the SQLServer parameter. I played around with adding a third parameter for Port but ran into issues with null values when the field was empty.
Again, this is excellent work, and it will be extremely beneficial to me and my teams.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
This is a great project, and it is exactly what I was looking to build myself. One suggestion, though, is that it would be much more useful if it wasn't dependent on (or expecting) Azure SQL. While the data collection script works with a local db, the report template does not. Since I am a complete novice with Power BI, it took a while to figure out why. With the port number hard coded in the queries, it prevents Power BI Desktop from connecting to a local SQL Server DB on the same machine. Once I modified all of the queries to remove the port number, the report ran like a champ.
I would suggest removing the port number from all queries and specifying that it needs to be included with the SQLServer parameter. I played around with adding a third parameter for Port but ran into issues with null values when the field was empty.
Again, this is excellent work, and it will be extremely beneficial to me and my teams.
Beta Was this translation helpful? Give feedback.
All reactions