Consulting Wrap Up – What Next and How to Get Started

You can apply these working rules yourself or ask me to join your team. This consulting wrap up brings the six-part series into one checklist and explains the four engagement options.

This is part 6 of my six-part consulting series. The next step depends on whether you need a fix, training, or another opinion.

Consulting Wrap Up: Five Principles and One AI Check

The earlier posts describe one way of working your team can inspect. They connect ownership, measured evidence, and retained knowledge. Each principle remains useful whether you book anything or handle the investigation yourself.

• Consulting 101 keeps your team at the keyboard, with no credentials handed over and no remote control.
• Consulting 102 lists what I promise: plain explanations, retained scripts, an undo path, and an action plan.
• Consulting 103 uses a focused window of up to four hours, with written next steps when work remains.
• Consulting 104 leaves every script, checklist, and prompt with your team so the checks can be repeated.
• Consulting 105 aims to leave the know-how to handle an understood cause while welcoming useful follow-ups and new problems.

The additional principle is that AI gets checked, not trusted. A generated recommendation needs evidence, review, and a recovery path. Treat its confident wording as something to evaluate rather than permission to execute it.

I ask whether the customer can explain the change when the meeting ends. That answer matters beyond the immediate symptom. The retained materials should support the team's next investigation.

Path A: Use the Process With Your Own Team

You can use the same working boundaries as an internal DBA helping another team. Agree on the problem and who approves changes. Keep the operator responsible for the execution context.

This checklist fits beside the query window during the review. It is the non-buyer takeaway from the series. Use your organization's approved records for the evidence and decisions.

• Keep individual credentials private and use an approved screen-sharing arrangement.
• Begin with scoped read-only diagnostics and the permissions those diagnostics require.
• Save each before-value and place a tested undo path beside the proposed change.
• Agree on the scope and finish with a written plan for remaining work.
• Hand over every script with its purpose, context, and read-only or change label.
• Confirm the cause from evidence instead of repeatedly treating its symptom.

Start by checking which server and database the window is connected to. Preserve the version and capture time beside your results. Those basic facts prevent comparisons across the wrong environment.

SELECT CONVERT(nvarchar(128), SERVERPROPERTY('ServerName')) AS ServerName,
       CONVERT(nvarchar(128), SERVERPROPERTY('ProductVersion')) AS ProductVersion,
       DB_NAME() AS CurrentDatabase,
       SYSUTCDATETIME() AS CaptureUtc;

Read the current values before discussing an instance configuration change. The following query changes no settings. Keep its result with the proposed change and its undo script.

SELECT name, value AS ConfiguredValue, value_in_use AS ActiveValue, is_dynamic
FROM sys.configurations
WHERE name IN (N'max server memory (MB)', N'max degree of parallelism',
               N'cost threshold for parallelism', N'optimize for ad hoc workloads')
ORDER BY name;

A Consulting Wrap Up for Anyone Starting a Practice

When I started consulting, I had no idea how to invoice, schedule meetings, or find customers. Those first business questions felt as pressing as technical questions. Learning the routine made room for the work itself. SQL Server doesn't grade the invoice layout.

How should I send an invoice, and how should I schedule the meeting? What belongs in the agreed scope? These were questions I needed to answer before the process became familiar.

For your own practice, separate administration from the technical diagnosis. Write down the agreed scope and the approval boundaries. Keep the first plan small enough to explain and carry through.

Don't hide an unfinished investigation behind an impressive invoice description. State what was checked and what remains. The paperwork shouldn't claim certainty the evidence hasn't earned.

If you want time to discuss starting a consulting practice, request an On-Demand Expert Hour at USD 650 per hour. Describe the questions in the first email.

Path B: Choose the Work You Need

My consulting work draws on 24+ years of hands-on experience with over 400 customers. The options have different purposes. Choose the purpose before choosing a calendar slot.

• Comprehensive Database Performance Health Check: USD 2,432 fixed price, up to four hours on Zoom, usually two to four.
• SQL Server Performance Tuning Practical Workshop: USD 2,432 per class, three to four hours live on Zoom for the whole team.
• AI Enablement Workshop for Data Teams: USD 2,432, up to four hours on Zoom.
• On-Demand Expert Hour: USD 650 per hour for follow-ups, second opinions, urgent problems, and recommendation checks.

There are no retainers or long contracts in these options. The Health Check has no hourly meter. The Expert Hour has its stated hourly rate, so keep that distinction clear when choosing.

Most Health Check fixes start within the first 75 minutes. Most changes need no downtime and no restart. The session still ends with an action plan when further work is needed.

You keep every script, checklist, and prompt used in the engagement. Every change gets a plain explanation and an undo path. Nothing is copied off your systems.

Check Whether the Working Arrangement Fits

The Health Check fits a performance problem your team wants to understand. Someone must be able to share the screen and run the scripts. You decide what to do, study, or skip for each finding.

The session doesn't provide an operator who logs in and fixes the server alone. I don't take remote control or receive usernames and passwords. Your team's approved operator stays responsible for execution.

A team needing training more than a fix should look at the Practical Workshop. A request for ongoing retainer coverage doesn't match these offers. State that need early so the scope remains clear.

For this consulting wrap up, the choice is a working fit rather than a promised performance percentage. Bring the actual question your team needs answered. That makes the first exchange useful.

Send the First Email With the Right Context

Email pinal@sqlauthority.com with the engagement you want or your problem in a few lines. Include SQL Server versions, company name, and time zone. Describe the symptom without sending passwords or private data extracts.

I reply with the earliest available times and payment options. We agree on the slot. Once payment is in, a Zoom invitation arrives for you to share with the team.

Payment methods are credit card, debit card, bank transfer, or PayPal. Once payment is made and the meeting is scheduled, it isn't refundable. Read that rule before completing the booking.

Decide who will operate SSMS and who can approve a change. Keep recent-change notes ready for diagnosis. Avoid gathering credentials or copying customer records for the meeting.

Close the Consulting Wrap Up With a Process You Can Reuse

What should your team be able to repeat after the call? Make that expectation part of the preparation. Retained scripts need explanations and context to become usable knowledge.

Use this consulting wrap up as a checklist for either road. See the Consulting page if you want to work with me. Keep the same ownership, evidence, and recovery standards when you do the work yourself.

Related reading on this blog: 5 Questions Answered: Comprehensive Database Performance Health Check and The Value of Skill: A Comprehensive Database Performance Health Check.

A useful engagement is not a meeting on the calendar, it is a process your team keeps.

Published by Pinal Dave on SQLAuthority. More of my work at pinaldave.com.