◆ Microsoft SQL Server

Get actual data size per row

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskGet the actual data size per row for the 'CustomerOrders' table in the 'SalesDB'…+
Get the actual data size per row for the 'CustomerOrders' table in the 'SalesDB' database.
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 acceptFor the 'CustomerOrders' table, calculate the average actual data size per row, including…+
For the 'CustomerOrders' table, calculate the average actual data size per row, including variable-length columns. Also, show me the maximum potential row size. I need to present this to the storage team to justify increased disk space for next year's growth projections.
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 'AuditLog' table is growing much faster than expected, and I need to understand why its row…+
The 'AuditLog' table is growing much faster than expected, and I need to understand why its row size is so large.
The 'AuditLog' table is growing much faster than expected, and I need to understand why its row size is so large. Management is asking for a report on storage consumption by end of day. I suspect some variable-length columns are storing more data than anticipated, but I don't know how to confirm this without impacting performance. What's the best way to get a breakdown of the actual data size contributed by each column in the 'AuditLog' table, without causing performance issues on the live system?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently underestimate the actual storage consumption of tables due to variable-length…+
I consistently underestimate the actual storage consumption of tables due to variable-length data, leading to inaccurate capacity planning.
I consistently underestimate the actual storage consumption of tables due to variable-length data, leading to inaccurate capacity planning and unexpected disk space alerts. This causes last-minute scrambling and budget overruns. What habit should I change in my database design review or monitoring process to more accurately predict and track the true storage footprint of tables, especially those with many variable-length columns, to avoid these surprises?
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.