sqlrockstar ✭✭✭✭✭

OK, two things here. First, NULLs are awful, vile creatures. If I could make NULLs into a ring I would throw them into a volcano. So I don't say this is a flaw in orion necessarily, but I don't know enough about how NULLs are (or are not) being handled. Needless to say, they are rarely handled well (as you can see).…

Ah, I see. In that case, you will want to isolate the queries coming from the front end and see what they are waiting for, as they might not be the same queries you are seeing with CXPACKET waits.

@"Utkarsh_srivastava" I don't believe this is possible at this time. The DPAIM allows for data from DPA to be displayed in Orion. However, DPA alerts are not included in the integration. @"cpriddy" might have more details to share regarding product roadmap for DPAIM. HTH

Triggers had a place in relational databases 20 years ago. Anyone building something from scratch today and using triggers should have their fingers smacked with a keyboard.

DPA is querying the sys.dm_os_wait_stats DMV and doing some math, something similar to this query: SELECT SUM(signal_wait_time_ms) AS [SignalWaitTime], SUM(wait_time_ms) AS [TotalWaitTime] FROM sys.dm_os_wait_stats WHERE wait_type NOT IN ( 'CLR_SEMAPHORE', 'LAZYWRITER_SLEEP', 'RESOURCE_QUEUE', 'SLEEP_TASK',…

I'm not certain how you will be able to do this without custom code, but I do have a follow up question for you...why does the fact that it is a new table matter? I'm trying to understand why I would want to exclude indexes on a table identified as "new". If a table is new, I would expect the indexes to be created…

I like that approach.

Joshua, I've no idea if this is the case or not...but are you allowed to modify indexes on the Orion DB without violating terms of support? If so, then you would be able to cure bookmark lookups. Of course, first thing would be to determine why the deadlocks are happening. The article I linked to shows ways to capture the…

Shrinking will NOT improve performance, you will only recover unallocated disk space. Shrinking is necessary when you need to get some disk space back, and shrinking will cause fragmentation that is likely to degrade performance. I'm sorry to see that anyone is recommending this. I'm not sure who to contact about this, but…

Signal waits are an indication of possible internal CPU pressure. The CPU Signal Waits metric is a rate of change metric. That means you can see a spike in signal waits from one minute to the next without the server itself showing a high CPU utilization for the server. With a virtual database server this could also mean…

Those are great questions, and it's where a product like DPA really shines by focusing on wait stats at the SQL statement level. Now, your original question about if the monitoring is causing issues...again, something that can be remedied by (1) shutting off the monitor or (2) letting DPA collect some details about the…

Well, my first question here would be "is there a problem"? I can see the aggregate amount of wait in the chart, but how many executions and sessions are running? Also, are you seeing any CPU pressure? What do the Signal Waits look like? It could very well be that you simply have a lot of queries running in parallel, but…

Do you have the name of the SW engineer that told you this? If so, can you email the details to thomas.larock at solarwinds.com. I'd like to help get this advice corrected going forward.

Nope. Not wearing them then, and not wearing them now. #NoPants

I'm a huge fan of where this is going. I don't think Microsoft is concerned with selling licenses of SQL on Linux. I think they just wanted to offer an alternative to Linux-focused shops that have been using things like Postgres for new development. By offering an alternative, these shops now have a choice. To me the real…

@"AdemirP" The Wait Time Chart is meant to serve as a guide, as described in the help file (located to the right of the chart): Compare I/O wait time with all other wait time for the database instance. Use this to help you determine if the primary cause of wait time is I/O related: * I/O could be the primary cause of wait…

@"hshi" DPA focuses on statements, not stored procedures. However, this post may be helpful: https://thwack.solarwinds.com/t5/DPA-Documents/DPA-Report-on-Stored-Proc-Impacts/ta-p/528447

@"[Deleted User]" DPA does not require an agent, it runs T-SQL to query DMVs and return data. WMI collection was turned off starting with version 10 (although you can enable this if desired). DPA also creates an xEvent session to capture deadlock details. This architecture allows for DPA to have a minimal footprint. The…

@"dkoceja" There are a handful of custom reports available here: https://thwack.solarwinds.com/t5/DPA-Documents/tkb-p/dpa-documents/label-name/sql%20server%20custom%20reports One of those should get you close. If you can't find what you are looking for, contact support and one of our SEs should be able to help you get what…

@"juddl" Here is a custom report that might help: https://thwack.solarwinds.com/t5/DPA-Documents/Custom-Report-Top-SQL-for-Database/ta-p/529535 The report is fairly old, I'm not sure if it will still work as expected. If it does not work, drop an email to support and ask for help in creating the exact report you need. HTH

@"rhether" At this time, you cannot use the API for this task. Your best option would be to contact support and ask for help in writing a custom script to update the DPA repository directly. HTH

@"mproper" Not at this time, no. You can always suggest this as a feature request and I can advocate on your behalf when it comes time to decide what features we get added to a future release. HTH

@"[Deleted User]" Yes, I consider the terms to be synonymous. DPA is using information from sys.dm_io_virtual_file_stats to display the data, just as Greg mentions in the article. HTH

@"SeanM" Not sure DPA sets the deadlock priority to be low. You could try putting this code at the top of the custom alert script and see if it works: SET DEADLOCK_PRIORITY LOW; <custom alert script here> HTH

@"often_confused_dba" Currently, DPA does not break out the worker threads in that manner. You will need to examine the query plan to find the operators that were running in parallel and examine to see if the threads had a balanced workload. HTH

There is already a long running job alert inside of DPA. It defines "long" as a job that is more than 2 standard deviations from the mean over the past 90 days.

I'll have a look at this and let you know, thanks for putting this together!

I put one in my son's coat, in an inside pocket that he never uses. He lost it anyway.

Oh! I have a tile app as well. I should think about using it.

For the record, the keys weren't "lost", they were just somewhere else, waiting to be found.