One screen, report or transaction is slow. Find out what to investigate next.
For teams investigating one slow operation on a reachable SQL Server, with a representative evidence window.
Get a timeline of the symptom, likely contributors and a plan for the next investigation. The report explains when SQL evidence points to a cause and when more information is needed.
A slow operation can involve queries, blocking, server resources or another layer of the application. Review the available SQL evidence before choosing the next investigation.
You collect. We assess.
Self-Service
Your team runs the BriteThought Diagnostic Collector in the agreed environment, reviews the package and sends the results. We provide expert analysis and the written assessment. BriteThought doesn't need remote access or your credentials.
Standard
$1,195
Priority Same scope, reserved scheduling
$1,595
USD · excluding applicable taxes · per engagement
You receive the expert-reviewed report and one written review of collection status. When useful, we also include one request to rerun failed or missing modules or provide a limited alternative.
We don't troubleshoot your permissions, security, network or execution environment in Self-Service. Remote sessions and a findings call aren't included; you receive the report in writing.
Standard target. Written delivery target: within five business days after complete intake and sufficient evidence are confirmed.
Priority target. Analysis slot within one business day after sufficient data is admitted; written report target two business days after data admission.
You arrange appropriate access through your approved process. We collect the evidence and carry out the same core assessment, with selected live validation.
Standard
$1,995
Priority Same scope, reserved scheduling
$2,745
USD · excluding applicable taxes · per engagement
You receive the same core written deliverables, up to 3 hours total of collection and the listed live validation or investigation, plus one 30-minute findings call. Recommendations aren't permission to change production.
Your team approves access and makes local security decisions. Production changes and remediation need a separate agreement. Access restrictions can still prevent collection.
Standard target. Collection is normally scheduled within five business days after scope, payment and working access are confirmed. The written report target is five business days after complete intake and sufficient evidence are confirmed, once collection is complete.
Priority target. Collection start within two business days after working access and scope are confirmed; written report target two business days after collection.
This is a one-time assessment with a fixed scope and the listed deliverables. Production changes and remediation are separate. With Self-Service, your team collects the evidence; customer-specific collection troubleshooting is excluded.
Priority requires confirmed availability before payment. We’ll confirm whether the service fits, the scope and the dates before payment. This website does not accept payments or diagnostic uploads. See when work starts and what can pause it.
One instance, one application, one named user database and one symptom, such as a screen, report or transaction timing out.
One representative capture window of up to 60 minutes, plus up to seven days of available performance history.
We review up to five relevant SQL statements or plans, waits, CPU and I/O indicators, and captured blocking or deadlock evidence. New tracing without agreed limits and application-wide instrumentation aren't included.
Managed includes up to three hours total of collection and interactive investigation, including one attempt to reproduce the problem in the agreed window, plus a 30-minute findings call.
A second symptom, another instance or another application needs a new agreed scope.
We may use instance-wide metadata for context. Detailed review of unnamed databases, additional instances, replicas or environments is excluded.
Your report
Findings, reasons and next steps.
The symptom timeline and what the evidence shows
You receive a timeline of the symptom, a triage conclusion supported by evidence, likely contributing factors with confidence levels, and a plan for the next action. If the evidence points to SQL, the report identifies the selected queries or configuration settings to consider. If the SQL evidence isn't decisive, it explains what application, infrastructure or further workload information is needed.
Both modes include an executive summary, the evidence sources and their limits, and recommendations that identify who should act, the risks and what needs testing. We supply candidate scripts only when an applicable, validated standard template supports a material recommendation. Custom scripts, code rewrites and execution are excluded unless expressly listed. Send up to five report questions together within ten business days of delivery for one included round of clarification. Managed includes one 30-minute findings call. Self-Service includes written delivery; a call can be purchased separately.
When is the assessment complete?
We complete the service when we've investigated the agreed symptom and delivered the written triage report. An inconclusive result can complete the work if the report supports that conclusion and records the tests, uncertainty and next step. We don't promise a percentage improvement or guarantee that timeouts will stop.
A time limit alone does not complete the service. We must document the investigation or executed test, its result and its limits. If required collection fails before we accept the evidence for analysis, the collection, upgrade and refund rules apply. An empty report is not a successful diagnosis.
What we’ll need
Your environment, the question and access.
The standard service covers one reachable primary SQL Server Database Engine instance on Windows, on premises or in a virtual machine you control. Its release and edition must be compatible with the current collector. A named instance counts as a separate instance.
Before you pay, we'll confirm the metadata permissions, approved host diagnostics and collection window, along with the exact permissions for your SQL Server version, runtime requirements, disk space and tested compatibility. Sysadmin or local administrator access isn't a requirement for every assessment.
Complex availability groups, failover clusters, replication, distributed applications, Azure SQL Database, Azure SQL Managed Instance, Linux, inaccessible hosting, unsupported versions, extra instances, replicas or environments need a review before we quote separately. Enterprise edition may qualify if the technical scope stays small.
Tell us what slow means for your team: the operation, how long it takes, how long you expect it to take, user impact, when it started, how often it happens and recent changes. Give timestamps with the timezone and a safe way to reproduce it. Identify the SQL database behind the operation and someone who can use the application during the collection window.
Your team arranges application access, test data that can reproduce the problem and vendor permissions. Don't repeat a transaction that changes business records without first agreeing a safe way to reproduce the problem. Evidence from a test environment may not represent production, so agree a safe, representative capture.
Collecting evidence
Check that the evidence can answer your question.
Permissions, security policies, endpoint protection, network restrictions, hosting, software configuration and familiarity with the collector can prevent some or all collection. We can't guarantee the collector will work in every configuration. Its initial checks and summary must show which modules completed, partly completed, failed or were unavailable.
Before analysis, we need the symptom and timings, instance and database identity, a representative capture window or enough historical evidence, and SQL activity linked to the operation. If the symptom wasn't captured, we'll explain and agree what can still be reviewed before accepting the evidence for analysis. An inconclusive result after that agreed review is different from having no useful evidence to review.
If Query Store or optional history is missing, we record the gap; it doesn't automatically mean collection has failed. We may agree to use a limited sample and available cached plans instead. We won't silently enable Query Store or persistent tracing. Restarts and how long cumulative counters have been running affect how we interpret the results.
Collection is designed to read diagnostic information and take samples within agreed limits. Reads still use resources, and some metadata operations can compete with your workload. We can't guarantee zero impact in every environment. Use an approved window and stop if the impact becomes unacceptable. Changes, restarts, index operations and new persistent capture settings need separate authorisation.
Where possible, we compare the operation's elapsed time with the SQL duration we can see. We separate time spent waiting from time spent executing, and consider blocking, CPU, I/O and query plans together. We record cumulative counters, resets, sampling gaps and unrelated workloads. One observation alone doesn't prove that storage, the application or the vendor caused the problem.
The report records how you defined the operation, the collection window, the type of bottleneck observed, selected SQL evidence, confidence and a prioritised test or change proposal. It separates likely contributors from proven causes and makes clear if the symptom wasn't captured.
If your environment prevents collection
When you can put Self-Service payment toward Managed.
If permissions, security, network, hosting or execution limits stop your team collecting enough evidence, we'll review the collection status and check that Managed collection is feasible. The credit applies to the equivalent Managed assessment of the same instance, databases and question. You don't need to prove who was at fault or blame the person running the collector.
Standard upgrade to the same service
Managed assessment
$1,995
Self-Service credit
−$1,195
Remaining to pay
$800
USD · taxes recalculated separately
Request the upgrade within 60 calendar days of your Self-Service purchase. We credit the product amount you actually paid, including any paid Priority premium, up to the agreed Managed price. Taxes are recalculated separately. Credits have no cash value and can't be transferred to another customer, product, environment or add-on.
A new Priority slot must be confirmed; a credit does not preserve an expired reservation. Requests to switch modes before analysis begins may use the same credit by agreement even without collection failure.
If Managed collection also can't proceed and analysis hasn't started, we cancel and refund the unperformed Self-Service assessment, including any unused Priority premium. If our collector has a defect, we must fix it, provide an agreed alternative or refund the assessment if it can't proceed. Collector defects must not force a paid upgrade.
An inconclusive report based on enough accepted evidence is different from a failure to collect the evidence. A completed assessment doesn't automatically qualify for a credit or refund. New symptoms, a wider scope or implementation need a new quote.
Cancellations and orders that aren’t ready
You can cancel for a full refund before we begin analysing accepted evidence or start Managed collection. Once work starts, we assess the work performed against the agreed deliverables; your rights under applicable law still apply. An order needs to start within 30 days. If it isn't ready by then, we'll send a reminder and agree cancellation or a written extension. Your agreement, supplied before payment, records the cancellation terms for the service.
Sharing technical evidence
Know what you’re sharing.
What the evidence may contain
Server and database names
Object and index definitions
File paths
Job history and error messages
Execution plans and query text
Query text and execution plans can include literals, parameter values or other sensitive information even when no table rows are exported. Don't assume diagnostic output is anonymous. Review the package before sending it and remove credentials or unrelated information.
Standard collection doesn't intentionally export application table rows, full database backups or passwords. Before sharing data, confirm the compatible collector and the evidence needed. If you can't share that evidence, talk to us before you pay so we can agree a suitable alternative or a different scope.
With Managed, we use named, temporary access through your approved channel, with only the permissions needed. That access is revoked when the work is complete. Permission to read isn't permission to make changes. Don't send credentials, query output, diagnostic packages, backups or sensitive records through general enquiries or ordinary email.
We use your diagnostic evidence to deliver the agreed service. Selling it, using it for public examples or model training, or sending it to external AI services needs separate informed authorisation and suitable agreements.
Use the enquiry form for a brief description of the problem. Keep credentials, query output, diagnostic packages, backups and sensitive records out of the form and ordinary email. Before you share evidence, we'll agree the scope, collection method and privacy, access and retention arrangements.
How long we keep the evidence
Raw packages and temporary working files have a 30-calendar-day retention window after report delivery or cancellation. Final reports are available for 90 days. We keep order and accounting records separately. Before collection, we'll confirm the arrangements and explain any delays deleting backup copies, legal holds or longer retention you've agreed to. This website has no diagnostic upload portal.
When work starts
Turnaround & Priority scheduling
These service targets apply after readiness and availability are confirmed. Enquire for a date; no Priority payment is accepted without a confirmed slot.
Standard
Written delivery target: within five business days after complete intake and sufficient evidence are confirmed.
Managed collection is normally scheduled within five business days after scope, payment and working access are confirmed. The report target starts after agreed collection is complete; collection and reporting are separate stages.
Priority Self-Service
Analysis slot within one business day after sufficient data is admitted. Written report target: two business days after data admission.
Priority Managed
Collection start within two business days after working access and scope are confirmed. Written report target: two business days after collection.
When timing starts and pauses
The clock starts only after scope acceptance, payment and required evidence or working access. BriteThought sends a readiness confirmation and dates. An upload receipt is not evidence acceptance.
The clock pauses for missing data, unavailable access, customer approvals, reproduction windows or an agreed third-party dependency. BriteThought notifies you of the reason, required action and revised dates. Pauses are not hidden and do not cover ordinary BriteThought workload.
Intake acknowledgement target: one business day. This acknowledges receipt; it is not completed technical review or an emergency response guarantee.
Hours and availability
Monday through Friday, 9 am to 5 pm America/New_York, excluding US federal holidays observed by the service.
Requests outside service hours enter the next business-day queue unless a separate appointment is confirmed. A symptoms window outside service hours needs a separately agreed appointment.
Priority requires confirmed availability before payment. Payment alone does not create an immediate response commitment. The booking confirmation states the actual reserved start and target delivery date. Priority changes scheduling, not scope, and does not provide remediation, after-hours coverage, continuous emergency support or a resolution deadline. An active outage, inaccessible server or suspected data corruption needs separate incident scoping.
If a confirmed Priority date is missed
If BriteThought cannot honour a confirmed Priority start or report date for reasons within its control, the Priority premium is refunded and the assessment retains its agreed scope. Customer delays and documented external dependencies do not trigger that remedy. Full cancellation and refund are offered when no agreed work has started and no replacement date is accepted. An unconfirmed slot will not be substituted after payment.
This is a one-time service with a fixed scope. You receive the agreed investigation or test and its written result. Production changes and remediation need a separate agreement, except for the operations expressly included in the isolated Recovery Proof test. We don't guarantee improved performance, uptime, identification of a root cause or recoverability. The service does not certify security or compliance.
Application rewrites, deploying index or query changes, restarts, memory increases, hardware changes, operating-system repairs and continuous monitoring aren't included. Recommendations still need any testing identified in the report.
This service does not include ongoing monitoring, unlimited revisions, an enterprise audit, compliance certification, licensing advice, an application rewrite, migration, hardware procurement, a production restore, corruption repair, representation in a vendor dispute or routine DBA work. It does not certify security or recoverability.
Why BriteThought
Careful analysis. A report you can use.
Evidence before assumptions
Reports distinguish what was observed, what may be contributing and what remains unknown. Each recommendation explains its evidence, its limits and the next useful test.
A specialist reviews the evidence
A qualified specialist analyses the evidence and is responsible for your report, using documented collection methods and review checklists. Consistent report formats and a process for further technical review support the assessment. Participation by a particular founder or engineer isn't guaranteed.
A report your team can use
Use the report with your team, vendor or chosen implementer. It sets out priorities, responsibilities and validation steps so you can decide what happens next. Production changes remain a separate decision.
Common questions
Before we start.
What if it is only slow occasionally?
Share the available history or arrange collection while it happens. This service includes one agreed window; continuous watching needs a separate service.
Will Urgent Triage get us back online?
It reserves accelerated investigation when available. It is not an outage recovery or resolution guarantee.
Can you diagnose the whole application?
We review one operation and its SQL evidence. A wider application investigation needs a separate scope.
Does Managed include making the recommended changes?
With Managed, we collect the evidence and carry out the investigation or validation listed for the service. You receive recommendations; making those changes or providing ongoing support needs a separate scope.
Does Priority include support around the clock?
Priority requires confirmed availability before payment. Payment alone does not create an immediate response commitment. The booking confirmation states the actual reserved start and target delivery date. Priority changes scheduling, not scope, and does not provide remediation, after-hours coverage, continuous emergency support or a resolution deadline. An active outage, inaccessible server or suspected data corruption needs separate incident scoping.
Can we share the report and ask follow-up questions?
You can share the report with your organisation, advisers, vendor and chosen implementer. Send up to five questions about it together within ten business days of delivery; one round of clarification is included. This does not include new evidence, symptoms or implementation. Managed includes one 30-minute findings call. Self-Service includes written delivery; a call can be purchased separately.
Is Self-Service just an automated report?
No. Your team collects the evidence, and a qualified specialist analyses it and writes the report. Self-Service costs less because your team handles collection.
What if our team can’t collect enough evidence?
We include one written review of your collection status and, when useful, one request for a targeted rerun or limited substitute evidence. Troubleshooting permissions, security, network or execution problems specific to your environment, and remote sessions, are excluded. If environmental limitations prevent collection, your payment may qualify for credit toward the equivalent Managed assessment, provided we can perform it. The upgrade rules on this page include a 60-calendar-day request limit. A standard upgrade leaves $800 to pay, excluding tax adjustments.
What if we can’t provide access for Managed either?
We confirm whether Managed collection can proceed before you upgrade. If we still can’t collect enough evidence and analysis has not begun, we refund the unperformed Self-Service purchase, including any unused Priority premium, under the refund rules on this page. If a defect in the BriteThought collector prevents the assessment, we must correct it, provide an agreed alternative or refund you if the assessment cannot proceed. Collector defects must not force a paid upgrade.
Can diagnostic collection affect production?
Collection is designed to read diagnostic information and take samples within agreed limits. Reads still use resources, and some metadata operations can compete with your workload. We can't guarantee zero impact in every environment. Use an approved window and stop if the impact becomes unacceptable. Changes, restarts, index operations and new persistent capture settings need separate authorisation.
After the report
Decide what happens next.
Query and index findings may suit Index & Query Tune-Up; broader configuration concerns may suit a Health Check. Agreed low-risk changes can be quoted separately through a Change Implementation Block. Findings about the application or host go to the responsible team with the supporting evidence.
You can take the report to your team, vendor or another provider. Any further work needs its own clear question and scope. You don’t need to buy another service to have the agreed report explained.
We agree a separate quote for optional follow-up work before it starts. It stays within that scope and does not add ongoing support or automatic charges. Your own team or vendor can act on the report without buying more services.
Tell us what’s happening, how it affects your business and what you want to find out. We’ll check whether the service fits, explain what collection or testing involves and agree when work can start. Please leave credentials and diagnostic evidence out of your enquiry.
This is a one-time assessment with a fixed scope and the listed deliverables. Production changes and remediation are separate. With Self-Service, your team collects the evidence; customer-specific collection troubleshooting is excluded. Priority requires confirmed availability. See scope, data handling and upgrade terms.
