-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose custom queries and/or the report queries in SQL Nexus so users can customize their data mining #239
Comments
@hacitandogan, would you like to think about this one next. The request here is to expose the actual query behind the report in case people want to use it for direct analysis in SSMS. I can demo if you'd like |
@PiJoCoder , sure I will check this one and ping you for the demo and sync. |
You can use logic similar to this (in server configuration report), where the text of the query is not exposed at first, but we can have some toggle +/- to show it |
I did a sample on one of the reports to test this. This is server configuration report , which has multiple datasets; Tried to keep it plain and simple but should we highlight that more or is this good ? |
I agree with you that plain and simple is good. I don't think we need to go fancy on this. One thing that I image is to add this at the bottom of reports, away from other report data so people don't get confused. Is that how you image it too? |
sample modification for microsoft#239
@PiJoCoder , I sent a PR for one report only so you can also see and test this. If we are OK with this , I can implement the same for all reports. |
Thank you! I'll test and let you know |
Looks great, @hacitandogan! Let's proceed with it. Thank you |
-this is completed for all the reports in the list without checking if the report is actually in use or not. -tested with the sample data and did not see any issues -exception is ReadTrace reports, we dont have the rdls for them and we inherit / borrow them from RML , not sure if we can do anything for them.
PR for review for #239 - Expose custom queries and/or the report queries
PR merged , closing this item. |
The text was updated successfully, but these errors were encountered: