Comments
-
There is not a way to do that within the product but you can query the repository directly. Here is are some examples. Oracle Repository : https://thwack.solarwinds.com/docs/DOC-172663 SQL Server Repository : https://thwack.solarwinds.com/docs/DOC-172609
-
awickham10, I checked around about this today. It seems that this is b/c when that feature was developed, the current versions of DB2 made the medicine worse than the illness... That is to say that monitoring blocking imposed too much performance overhead. We think this may have improved since then. We suggest you take a…
-
You can tell DPA to exclude SQL statements for a particular SQL hash. So right after you start your profiler or tuning adviser, if you are getting a consistent hash for the activity, you could tell DPA to ignore it henceforth by running the following T-SQL against your repository database. INSERT INTO con_qp_exclude VALUES…
-
Deltona, the answer is a great big, "it depends". CXPACKET is one of those mysterious wait types. It doesn't necessarily mean there is a problem but you can experiment with reducing the Max Degree of Parallelism on the server. Sometimes reducing the degree of parallelism helps, sometimes it doesn't. Then there is also a…
-
Maybe it could be worded better in the hover/tool-tip. In the second view, "Total Wait Time for Time Period" is reporting the wait time for the whole bar you are hovering over (including all swatches of the histogram). 17 minutes and 45 seconds is 1,065 seconds and the y axis label seems to agree.
-
Thanks for reporting this. We will review and follow up.
-
Ahh, an opportunity to render my favorite answer. "It depends." ;-) It is fine for DPA and SAM to each have their repository on the same database instance and I believe I've heard of a customer doing it. That said, if the database instance is tight on resources, the experience may not be good.
-
Well any good question starts with it depends. My questions : What is the query load like? Mostly ad-hoc or mostly compiled stored procedures? I'm curious if data cardinality is causing the optimizer to build new execution plans instead of recycling old ones. Of course I have to ask why you want to achieve 100% Procedure…
-
The reason it requires 2008 is this metric is being gathered from the ring buffer which is part of extended events and that didn't come out until SQL 2008.