Comments
-
So not sure how you are going to schedule the job to run (SSMS or cronjob or ??), but here's what you will want to do: take a look at COND in the DPA repository. That table has the info you need and updates directly to it (be careful of course) can cause action to be taken - like starting monitoring programmatically.…
-
I'd recommend opening a support case at this point. May need to do a screenshare and dive in. How different is the new (clustered) index from the one you implemented on the 6th?
-
There are others... I think 2 more Easter Eggs. 8 )
-
Great warning! I'd have done the same thing you did!
-
If you are SURE you don't want any data related to that instance, then yes, you can do it manually. 1. select id, name from cond order by name; -- find the entry for this database and get the ID 2. Take a backup of the repo just in case. 8 ) 3. delete from cond where id = <the id from above>; 4. Drop all tables that end…
-
Try this one out. It's goitng against the daily metrics rollup (so won't have today's data). The advantage is the max and avg are already computed and stored, so you can see both or just use the one you want to report on... I haven't run this in test yet, so let me know if it errors out. I can test tomorrow. SET…
-
OK, using a custom alert on this one may be tricky as this is an inverted value (you will want to alert when it goes BELOW a certain number). Any reason not to use the default alert for resources? You can adjust the thresholds globally or for specific instances if you need to customize it a bit.
-
You could wrap it in a cursor that pulls the ID column from COND and then loops through all instances by appending the ID value... Food for thought.
-
We can only capture the text if it's running from within a procedure. Since this is dynamic, I think it's just a straight SQL Statement. The reason I was told is that it isn't a simple join and low cost query to get the SQL text for dynamic SQL in Sybase... You should be able to see other metadata about that hash though to…
-
Manu0417 - on your DPA app server, navigate to this directory <install_dir>\iwc\tomcat\ignite_config\idc\metrics\userdefined and look for a file called userdefined-metrics-properties_SQLServer.xml. Open that file and search for the custom metric you created. In the xml tags you will see property called displayName. That…
-
Should have mentioned this *should* work for hashes also, but you'd have to name the hash with a custom name, then use the custom name in the insert statement. Example would be: insert into CON_COLOR (TEXTSTRING, COLOR) values ('RobQuery1',33023) May need to go to options -> support -> clear chart cache, then wait a bit…
-
Kill the ghost process and see who gets upset?
-
Next body drop 5/1 @ 0 dark 30 (local time). 27.9878° N, 86.9250° E Bring a jacket.
-
deannich, DPA does not track buffer cache usage by database. We track at the instance level. So your assumption is correct about the limitation at the database granularity. Regarding PLE, your algorithm to show percentage of time that PLE is healthy (above 600) seems reasonable. I'd say that going after inefficient queries…
-
Since you know the alert fired, you can then go back into trends in DPA and look at the detailed deadlock information. Click on one of the events and you'll see the queries involved, who survived, who was killed, impact, deadlock priority, etc. See screenshots below. Is that what you had in mind?
-
Hmmm, so the SSD was really the performance improvement for WRITELOG. Do you know what kind of storage your transaction logs are on when not Netapp SSD? I guess what I'm asking is are they on RAID 5 or a RAID that may be doing parity calcs when doing write operations? A good thing at this point would also be to start…
-
Can you confirm that the hash excluded is no longer being collected? In the repo, run select id, name from cond -- use the id for the correct instance in question and substitute it for the <id> placeholder below select izho, max(d) from consw_<id> where izho = 2800065850 Let's see when the last collection date was for this…
-
Here is a report for top SQL by database. It looks like it's for 1 database at a time, but you could loop through it excluding system dbs easily enough: Custom Report - Top SQL for Database
-
So I think we may be talking apples and oranges on this one. Here's some explanation that I hope helps: * For the "Blocked Sessions" under resources, we actually query the monitored instance with the below SQL, then plot that per the interval using a diff in java. You could use the same query and specify whatever timeframe…
-
DPA summarizes into hourly and daily waits/stats. By choosing a custom time interval, those charts will be at least partially built out of the detail data putting additional load on the database.
-
Ok, so for read consistency, the selects could be causing the blocking. Feel free to reach out to support for anything else also.
-
Did you try in connection properties also? Shouldn't matter. I strongly encourage you to submit a ticket with support at this point as this will likely need to go to engineering.
-
Here's the article I was referring to: SolarWinds Knowledge Base :: Update to the latest jTDS driver for DPA 9.2
-
A support ticket might be the best option in this case. Did you try looking at the options? From the home page, for the instance in question, select the action dropdown and choose advanced options. Make sure the support options is chosen and you'll have to scroll down to more than half way so that you see the instance…
-
Wow - looks like it's not even trying to insert a value for PUB. INSERT INTO CONTT_5 (CNT, IEDX, QP, SP) SELECT ?, ?, QP, SP FROM COND WHERE ID = ? Not even accounted for in the insert statement...
-
What OS are you running DPA on? It's easier on linux as you just have two homes, but with windows, we create a service, so to do it on windows, there's a manual workaround that I can send you if you do want to go that route.
-
When looking at the 30 day trend, we pick out the top 15 SQL statements with the highest wait time to show taking into account the entire 30 days. When you drilled into the 24 hour period on the 10th, that shows the top 15 SQL statements for that time period taking into account that 24 hours. What I suspect happened…
-
You can pull that data, but you will have to do it using WMI calls via SQL Server. We had metrics using OLE automation in prior versions and went away from them due to security concerns and stability issues (WMI calls going out to lunch and never returning). If you want to pursue this course, you can look at the…
-
Do you have a field that gets updated with a current timestamp upon inserts? Might be an easier way to tackle this.
-
To sqlrockstar's point, if you click on a specific day and set the interval to be 1 day, click on that large aggregated bar. Then go to waits and click on CXPACKET. That will show you which SQL statements are contributing most to the CXPACKET wait type. Having said that, I've done some investigation into CXPACKET waits and…