What problem does it solve? Working with a SQL database in Microsoft Fabric requires juggling schema authoring, read-only querying, and performance diagnostics across T-SQL, REST APIs, and CLI tools, and mistakes like hitting the wrong endpoint or guessing workspace IDs waste time and produce wrong results. ## Core Features & Use Cases - Schema Authoring: Create tables, constraints, indexes, vector columns, and temporal tables, run DML, and deploy dacpac files via SqlPackage against a Fabric SQL database. - Read-Only Querying: Explore catalogs, run SELECT queries, perform vector similarity search, and execute temporal queries through sqlcmd with Entra ID authentication. - Performance Diagnostics: Investigate Query Store data, live and intermittent blocking, regressed plans, wait statistics, and CPU/IO pressure using DMVs and Extended Events. - Use Case: When users report intermittent slowness, run volatile query detection against Query Store, follow the wait-category decision tree, and identify whether blocking, plan regression, or resource pressure is the root cause. ## Quick Start Ask the assistant to create a table, run a query, or diagnose slow queries in your Fabric SQL database, and it will pick the right mode and execute the commands.