SQL Server performance (slowness)

A support ticket cannot be opened directly from here. To get Microsoft support for SQL Server performance issues in a production environment, create a technical support request through the appropriate Microsoft support channel or via the Azure portal if the workload is on Azure.

Before opening the ticket, collect as much performance data and problem description as possible. For SQL-based business applications (such as Dynamics or other line-of-business systems), support engineers typically expect at least the following:

1. Clear problem description

• What is slow (specific queries, reports, posting, batch jobs, application screens)?
• When it happens (time of day, after deployments, after upgrades, only under load)?
• Who is affected (all users, specific locations, specific roles)?

2. Repro steps and scope

• Exact steps to reproduce the slowness.
• Whether the issue is consistent or intermittent.
• Whether it occurs from all client machines or only some.

3. Performance and diagnostic data

• SQL Server error logs and Windows Event Logs around the time of the issue.
• Performance data focusing on CPU, memory, and especially disk I/O and latency (for example, via Performance Monitor/PerfMon).
• Any trace or profiling data (SQL Profiler/Extended Events, application profiler, or in-app tools if applicable).

4. Environment and recent changes

• Version and edition of SQL Server.
• Hardware/storage details and any recent firmware/driver changes.
• Any recent configuration changes (SQL Server settings, OS changes, network changes, antivirus, etc.).

If the performance issue is related to a Microsoft business application such as Dynamics 365 Business Central or Dynamics GP, use the built-in troubleshooting tools first (profilers, telemetry, trace logs) and then escalate with the collected data:

• For Business Central, use the in-client Performance Profiler and telemetry as described in Performance Profiler Overview, then raise a support case as described in Escalate Support Issues to Microsoft.
• For Dynamics GP, collect system information (msinfo32), Dexsql.log, SQL trace, SQLDIAG output, and Application log entries as outlined in the troubleshooting guidance, then contact Microsoft Technical Support with that data.

If the environment is hosted by a third-party cloud provider (such as Nournet Cloud), also open a ticket with that provider, since network, storage, or virtualization configuration in their environment can be a root cause. Provide them with the same performance data and timelines so they can check their infrastructure.

References:

• Report a performance issue
• You experience slow performance when you do specific processes in Microsoft Dynamics GP
• Troubleshoot slow startup and performance issues on a failover cluster that runs SQL Server
• Troubleshoot entire SQL Server or database application that appears to be slow
• Support for Intelligent Recommendations
• Open a support ticket for Azure Stack Edge and Azure Data Box Gateway