◆ Microsoft SQL Server

Install SQL Server following best practices

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 taskInstall a new database instance on 'DBServer03' for the new HR application. Use the default…+
Install a new database instance on 'DBServer03' for the new HR application. Use the default instance name, set up a dedicated service account 'SVC_HRDB', and ensure it's configured for mixed-mode authentication. I need it ready for the HR team to start testing by Friday.
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 installing the database for the new inventory system, review the system requirements and…+
Before installing the database for the new inventory system, review the system requirements and our company's security policies. Configure the instance for optimal performance and security from the start—this means proper collation, memory allocation, dedicated service accounts, and robust backup settings. Ensure it's resilient enough to handle future growth and compliance audits.
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 installing the database for the new financial reporting system, which will handle sensitive…+
I'm installing SQL Server for a new critical application, but I'm unsure about the best security configuration.
I'm installing the database for the new financial reporting system, which will handle sensitive data. I need to ensure it's secure, but I'm torn between using Windows Authentication exclusively or enabling mixed mode for some legacy integrations. The procurement lead is pushing for a quick rollout, but I'm afraid of creating a security vulnerability. What's the recommended security approach for a high-stakes financial system, and what specific hardening steps should I prioritize during installation?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEach time I install a new database, I find myself making ad-hoc decisions, which results in…+
Every new SQL Server installation feels like starting from scratch, leading to inconsistencies.
Each time I install a new database, I find myself making ad-hoc decisions, which results in inconsistent configurations across our environment. This makes troubleshooting harder and increases security risks. What habit should I cultivate to standardize our database installations, ensuring best practices are consistently applied and documented, so future deployments are predictable and reliable?
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.