Office Hours: Github Copilot in Azure Data Studio

I start by playing with the very underwhelming Copilot in ADS, then take your questions from pollgab.com/room/brento. Here's what we covered:
00:00 Start
04:06 Github Copilot in Azure Data Studio
24:36 Byron: Seeing plan cache queries for a long since retired table. What is best way to track down the app querying this table?
25:57 Eduardo: What is your opinion of ApexSQL SQL Plan viewer? Feels like a competitor to SQL Sentry Plan explorer.
26:33 SQLrage: Are their any tips or tricks (that aren’t out there regarding patching or page lock in memory) to prevent Non Yielding Scheduler errors related to IO issues? Seeing it a lot in a high transaction system and MS comes back stating IO problem is the root cause. Thanks brotha!
27:23 GP Geek: I've a case where Index REBUILD runs every week, but the DB tables keep showing a fragmentation of over 98% every day.. what's wrong ?
28:05 Nicolai: What is your opinion of the Microsoft MVP award?
32:37 Mr. SqlSeeks: When using a UNION operator to join the results of multiple queries, does the order of the queries affect how SQL Server gets the data?

[@luislema3863]

Raise the hand whom want Github Copilot in SQL Server Management Studio... 🖐

[@solovoypasando]

I really thought that with the extension, it would know the db structure and use that for the suggestion.

[@roland7642]

try adding:
-- Language: tsql
[ -- Coding style: upper / lower case ]
to help Copilot with the context
This also seems important to help with yaml and maybe other cases too
e.g. for Ansible playbooks
---
# Language: Ansible

[@BrentOzarUnlimited]

That seems... like a pain in the rear. I'm literally connected to a SQL Server. Why on earth doesn't the tool know that?

[@JonathanSwiftUK]

Maybe ask it to write some code which does different types of table joins.

[@andytroo]

13:28 - and that confidently completely wrong output is the downfall of language models - what is the correct next text here only works well when it has examples quite close to what you want.

[@mico77720]

If anything, this promotes for sql developers to document their procs