Enhancing SQL database in Fabric: share your feedback and shape the future
SQL database in Fabric is currently in preview, and we are actively rolling out improvements as we progress towards general availability (GA). Your insights play a crucial role in this journey. Whether it’s challenges you’ve encountered, features you adore, or any suggestions for enhancement, we want to hear it all—the good, the bad, and the ugly!
In this blog post, we will discuss the various forums available for you to provide feedback or get support. We’ll also explore best practices for communicating your needs, helping us prioritize our roadmap effectively. Your feedback carries significant weight and directly influences our planning and development efforts. Join us in shaping the future of SQL Database in Fabric by sharing your valuable thoughts and experiences.
–
Provide contextual feedback in the Query Editor
In the ribbon of the SQL database query editor, you’ll find a feedback button that allows users to submit product feedback, report issues or blockers, and request new features. This button is conveniently located in various feature inside the query editor, such as the performance dashboard, security management UI, and copilot, among others. This setup enables users to provide detailed, context-specific feedback pertinent to their current tasks and helps product managers efficiently locate and prioritize this feedback on the backend.
–
Best practices
Please ensure you do not provide any private or sensitive information. However, to most effectively help us improve the product, provide as much detail as possible –
–
Scenario #1 – Reporting an issue:
If you encounter a blocker, include:
- Specific error messages (if any).
- Steps to reproduce the issue.
- Any solutions you’ve already tried.
–
Example of effective issue reporting:
“Copilot sidecar chat was working fine at the beginning, but when I asked how to create a new report, I receive the error message ‘Unable to process request.’ I tried submitting a few more prompts, but I keep on getting the same error message. I’ve tried opening a new chat session or refreshing the browsers, but the issue persists.”
Ineffective issue reporting:
“Feature not working and shows a system error.”
Why? This lacks details about when and where the issue occurs, making it harder to diagnose.
Even better:
Open a support case via Fabric and Power BI Support or share your issue in the community forum. This ensures you receive professional assistance promptly and helps our engineering team to gather the necessary information to reproduce and resolve the issue as quickly as possible.
–
Scenario #2 – Requesting a new feature
If you have a feature request, describe:
- A detailed description of how you’d like the feature to work.
- Your specific needs or business scenarios where the feature would be beneficial.
–
Example of effective feature request:
“Would it be possible to bulk delete queries? This would be incredibly helpful because currently, with the query auto-save capability, we need to right click a saved query and delete it one by one, which is time-consuming. A feature that allows us to multi-select multiple queries and delete them in bulk would significantly improve efficiency.”
Ineffective feature request:
“Add a feature to help me figure out how to make query performance better”
Why? This request is too vague and lacks specific details about the information required to diagnose performance issues and implement optimizations, making it difficult to develop a targeted feature solution.
Even better:
Submit your idea so others can see and upvote it, helping the team prioritize development based on user demand.
–
Scenario #3 – Provide general feedback
When sharing general feedback or sentiment, it’s important to explain what you like or don’t like in detail—and why. This helps the team understand your perspective and make informed decisions about improvements.
–
Example of effective feedback:
“I really appreciate the intuitive interface of the query editor. The color coding and Copilot auto-complete features significantly enhance my productivity by reducing errors and speeding up the query writing process. However, I find the loading time for larger datasets to be quite slow, which affects my workflow.”
Ineffective feedback:
“The editor interface is good, but too slow”
Why? This feedback lacks specific details about which aspects of the interface are appreciated and which parts are slow, making it difficult to identify and address the issues effectively.
–
Wrapping up & next steps
To summarize, there are multiple ways you can submit your feedback or get help:
- Use the editor feedback button directly within the platform.
- Submit your idea on the designated idea submission page so others can see and upvote it.
- Open a new support case for immediate assistance.
- Join discussions or ask questions on the SQL database section of the Microsoft Fabric Community Forum.
To ensure your feature requests are effective and actionable, always provide detailed descriptions and specific use cases. This will help the development team understand the context and prioritize accordingly.
If you haven’t already started exploring SQL database in Fabric:
- Begin by signing up for a 60-day Fabric free trial.
- Enable SQL database in your tenant settings.
- Learn more via MS Learn:
