◆ Microsoft SQL Server

Document database schema

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All Microsoft SQL Server tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskGenerate a documentation report for the 'HumanResources' schema, including all tables, columns,…+
Generate a documentation report for the 'HumanResources' schema, including all tables, columns, data types, and primary/foreign key relationships. Save it as a markdown file for the new developer.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptThe new analytics team is starting next week, and they'll need to understand our core 'Sales'…+
The new analytics team is starting next week, and they'll need to understand our core 'Sales' database. Can you document the schema in a way that highlights the most critical tables and their relationships for sales orders and customer data? Include brief descriptions of what each key table represents, making it easy for a non-DBA to grasp the structure.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe compliance auditors just hit us with a demand for a full data dictionary of all PII in the…+
A new regulatory compliance audit just landed, and they're asking for a complete data dictionary for all PII data within the 'Customers' database by end of day.
The compliance auditors just hit us with a demand for a full data dictionary of all PII in the 'Customers' database by 5 PM. I know some columns have sensitive data, but it's not consistently named or tagged. I'm afraid I'll miss something critical and we'll fail the audit. What's the quickest way to identify all potential PII columns across the entire schema and generate a concise report that satisfies their immediate need?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly repeating myself explaining the same core database structures to new hires and…+
Every time a new team member joins or a new project starts, I spend days explaining the same core database structures.
I'm constantly repeating myself explaining the same core database structures to new hires and project teams. It eats up my time and delays their ramp-up. What habit can I adopt to keep our schema documentation consistently up-to-date and easily accessible, so I'm not the bottleneck for every new person trying to understand our data?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Microsoft SQL Server's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.