◆ C#

Perform bulk updates with Entity Framework

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 C# tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskUpdate all customer records in the database where their 'Status' is 'Pending' to 'Active' using…+
Update all customer records in the database where their 'Status' is 'Pending' to 'Active' using Entity Framework, ensuring the 'LastUpdated' timestamp is set to now for each record, and commit this by 3 PM.
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 I run this Entity Framework bulk update script to reclassify all 'Tier 2' customers to…+
Before I run this Entity Framework bulk update script to reclassify all 'Tier 2' customers to 'Premium', review it for potential deadlocks or excessive memory usage. Make sure it completes within an acceptable timeframe, especially given the 500,000 records involved.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm trying to update 100,000 product prices using Entity Framework, but it's taking hours and…+
My Entity Framework bulk update for product prices is taking too long and locking tables.
I'm trying to update 100,000 product prices using Entity Framework, but it's taking hours and users are reporting database timeouts. The procurement lead, Sarah, needs these prices live by morning. I'm afraid I've chosen an inefficient approach, possibly loading too much into memory or creating too many individual update commands. What's the most likely bottleneck, and what's the best strategy to complete this update quickly without causing further disruption?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep losing time and accuracy when performing bulk updates or queries with Entity Framework…+
I frequently run into performance issues with Entity Framework for large datasets.
I keep losing time and accuracy when performing bulk updates or queries with Entity Framework on large datasets. My code often performs poorly, leading to frustrated users and missed deadlines for data refreshes. What habit should I change to consistently write more performant Entity Framework operations for significant data volumes?
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 C#'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.