How do I convince my DBA there's a sporadic issue with the SQL Server?

The issue: basically, major slow down... Some queries, generating execution plans, even generating scripts of existing DB objects can sometimes take forever. Even operations that should have no performance issue, like generating the create table script, can sometimes take forever.

The situation - I have a SQL Server database on which I can create tables / views / etc..

The DB is hosted on a SQL Server (MS SQL Server 2016) managed by the company's IT.

I've asked him to look into it, and I believe he's been earnest in checking logs and he says the load on the server at times I noticed massive performance issues showed nothing out of the ordinary. In fact, he said it was all under 5% (very low).

I have the exact same code and queries running in staging and development environments, it's fine there - it's even super speedy relative to the production environment.

I'm at a loss at what could be the issue to be honest. And I don't know where to start.

closed as unclear what you're asking by hot2use, McNets, Erik Darling, dezso, LowlyDBA Jan 16 '18 at 14:30

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    You'll have to add a lot details to your questions for us to help you. How are you accessing the database/server? (tools, protocols, network, firewall, ....) How far apart are you from the database server? (network) Where are the staging and development databases located in relation to you and the production database.... – hot2use Jan 16 '18 at 8:22
  • 3
    Have you checked for blocking and locking? Wait stats at the time of the slow down? Has your dba got any monitoring in place, these sorts of intermittent issues can be very difficult to track after they've occurred if there's no monitoring in place. Personally, my first port of call would be to set up a job to collect wait stats at a regular interval, these can be very useful in highlighting pain points. – David Fowler Jan 16 '18 at 10:31

Start with Tara Kizer's post on Getting Help with a Slow SQL Server. (Disclaimer: it's on my company's blog.)

She walks you through:

  1. Getting your server's wait stats since startup with sp_BlitzFirst @SinceStartup = 1
  2. Getting server health data in Markdown format so you can copy/paste it into your Stack question with sp_Blitz @OutputType = 'markdown', @CheckServerInfo = 1
  • I would definitely recommend BO's sp_blitz – Shanky Jan 16 '18 at 11:14
  • 3
    @Shanky see, now, that's why I use my middle initial too. BGO. ;-) – Brent Ozar Jan 16 '18 at 11:29

Not the answer you're looking for? Browse other questions tagged or ask your own question.