Executable Troubleshooting Guides with Notebooks for SQL People
summary
Executable troubleshooting guides use Azure Data Studio notebooks to run real diagnostics and capture results: a ready bp_check notebook contains ~30 queries, results save into the .ipynb clone and can be run across many servers with Invoke-SqlNotebook, producing one output per target for later comparison. PowerShell notebooks and the powershell notebook module support parameterized runs, conversion from .ps1/.sql, and automation; conversions handle ~2–3k lines before splitting.
AI-written summary · about
chapters (19)
- 0:00Start
- 1:36Introduction to Trs and Notebooks
- 3:13Notebooks in Azure Data Studio
- 3:35Azure Data Studio
- 4:49Text Cell
- 5:37Code Cell
- 7:00Converting a Cell To Code Cell
- 10:09Troubleshooting Notebooks
- 22:03Powershell Notebook
- 23:35Convert Your Files Over to Notebooks
- 25:21Export Power Bi Assets
- 29:13Sql Assessments Notebook
- 31:26Is Azure Data Studio Free
- 31:57Extension to Azure Data Studio
- 33:12Rich Text Editing
- 38:39Sql Assessment Api
- 40:01Export to Notebook Ui in Azure Data Studio
- 41:54Quick Tips
- 43:36Takeaways
related talks
25mFrom Data Exploration to Modeling to Deployment
10mHow can you use prompt engineering to debug PowerShell?
01h 25mTroubleshooting your Data Workflows with Noteable+Dagster-live debugging of failed jobs
01h 09mAzure SQL Database Development Inner and Outer Loops
20mExcellent Database Adventure: From Code Errors to Reliable Releases
48mConnecting the dots of Azure SQL DevOps
01h 18mProductionizing Jupyter Notebooks
39mGet a Load of this - Realistic Load Testing for Power BI, explained!