◆ Microsoft SQL Server

Identify columns causing data truncation

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 taskIdentify all columns in the `CRM.Leads` table that are currently experiencing data truncation…+
Identify all columns in the `CRM.Leads` table that are currently experiencing data truncation issues when new data is inserted. I need a list of the column names and their current definitions.
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 acceptBefore the next data import from the external marketing system, I need a comprehensive check of…+
Before the next data import from the external marketing system, I need a comprehensive check of the `Sales.Contacts` table for potential truncation. Show me not just existing issues, but also any columns where the current definition is too small for the expected incoming data, considering the usual length of the source fields.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentUsers are reporting that employee names and addresses in the `HR.EmployeeDetails` table are…+
Users are reporting garbled or incomplete data in the `HR.EmployeeDetails` table, and I suspect truncation, but I don't know where to start looking.
Users are reporting that employee names and addresses in the `HR.EmployeeDetails` table are appearing garbled or cut off. I suspect data truncation, but with many columns, I don't know which ones are the culprits or why. I'm afraid of making a schema change without understanding the root cause. How do I quickly identify all columns suffering from truncation and diagnose if it's an insertion issue or a display problem?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently discover data truncation issues only after users report incomplete data, leading…+
I frequently discover data truncation issues only after users report incomplete data, leading to reactive fixes and loss of data integrity.
I frequently discover data truncation issues only after users report incomplete data, leading to reactive fixes and a loss of data integrity. This impacts the reliability of our reports. What habit should I change to proactively identify potential data truncation risks in our tables and data pipelines, allowing me to address them before they impact users and compromise data quality?
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.