mandevil · Product Manager · ✭✭✭✭✭

Yes, go to Options -> Management API Options for a list of features/data you can consume data from using gets. If it's not exposed via an API, there is the potential to query directly against the DPA repository. This community site has some content you might find helpful in this…

No, it's actually methodology. We do sampling, so can't tie anything caught in-flight with a specific batch run. You might want to look at Database Insights where you can add SQL Sentry which would capture the sproc runs... Since you already have DPA, it's extremely cost effective.

We capture the individual SQL Statements that may run from a SProc. However, if you would like ot see overall impact of top SProcs running in your env, try this custom query against the repo: Custom Report - Top Stored Procedures 

If there is not a limit on number of files, then does monitoring at the volume/drive level likely makes more sense?

Sounds like a plan - wishing you smooth sailing!

Hi Dave, DPA should work just fine with 2016 (both Windows and SQL). The reason we had to delist 2016 is that it is officially outside of normal support by the vendor (Microsoft). So best to not put Solarwinds into a technically exposed situation by stating we support a version on which we can't get vendor support. Hope…

Hi Nutchi, not sure I have enough information, but there are a couple of things going on here. The first is just an index recommendation coming from Microsoft SQL Server, not DPA. I will leave it up to you whether that index is a good recommendation or not - we just want to make you aware in DPA that the index…

This one looks to be credentials related. When the repository was created, we record the repo schema user and PW in the repo.properties file (PW gets encrypted on restart of DPA). Assuming from the post that your repo is on SQL Server, can you run SSMS from the DPA application host/VM and see if you can authenticate with…

Couple of things you might try just off the top of my head: * Have the person that installed on their PC uninstall all SQL Sentry binaries and reinstall just the client * On the server, make sure that monitoring service can startup and stay started - pay close attention to the version of the monitoring service on the…

Had a chance to attend and speak at SQLBits 2023 in Wales with these fine gentlemen and Sophie! Great event and chance to connect with many of our customers over the pond.

If you just want to demo DPA and Orion capabilities, you might consider just using our public facing demo sites. DPA site: https://database.demo.solarwinds.com/iwc/login.iwc Orion site: https://oriondemo.solarwinds.com/Orion/Login.aspx?sessionTimeout=yes&ReturnUrl=%2fOrion%2fDPA%2fSummary.aspx If you were looking to use…

Not sure how much can be posted on our community site here, but if you reach out to support, this is something that we have shared previously - meaning the full ERD... However, this looks like a good start!

As mentioned here, I think a custom report is your best bet. * Click into reports * select "Top SQLs" as the report type * Select "User-Defined SQL Statements" * Click the Add button * Type in the identifying SQL text like "insert into nodes" or whatever you are looking for * Search - and make sure you are searching SQL…

How many instances are you monitoring? You might have to break the alerts out to look at just a specific instance (add 'AND id=<id from COND>' to the alert SQL).

No hurry, but would you mind adding this as a custom alert for SQL? Good to have as a document as well as in the thread… Rob Mandeville | Senior Product Marketing Manager | SolarWinds Office: 303.245.6879 | Mobile: 303.591.1019

When you query the COND table, what does it show for command and status for each instance? The script I added will only flag instances that *should* be monitored but are not for some reason (like an error). Make sure you aren't expecting an alert if you stopped a monitor manually because the command in that case would be…

Let's do that. I just emailed you some slots for early next week.

David, email me offline and we'll work out a time.

Sorry about that - I knew we had the data in the repo, just didn't think about that specific limitation when I started writing the query...

Great to hear!

I see a couple of issues. Try this SQL using a custom multi-numeric return. select NAME+' Monitor is stopped', 1 from [ignite].[COND] WHERE [STATUS] = 'STOPPED' and [COMMAND] = 'START' This will prevent you getting alerted when the monitoring was turned off explicitly (command set to STOP) - which assuming would be a false…

Wanted to check in and see who things were going? Any luck engaging with the vendor? Want to schedule a slot to take a look in real-time? This is not a support issue (recommend closing that out - sorry, that wasn't good advice from me). There may be a couple other views (like blocking correlation tab) that can help…

Sounds like a plan!

Do you have access to your customer portal? If you do, you should be able to open a case directly from there for DPA (under the support tab). If you don't have access, you can send an email to customerservice@solarwinds.com and request access by providing your SWID.

bmrad​, aiglee.castillo​ - the PM has been notified here of your interest in the beta. Thanks!

No, that's not a lot. 8 ) I was thinking it may be a volume related issue, but not seeing it in that number. I think you are on the right track with the parity calc overhead at the storage tier where the transaction log lives. That being the case, there is another thing you can check. Go to the Storage I/O super tab in…

I love the idea - feature request? See jaminsql's comment up above.

email me - I'll send you and invite... robert.mandeville@solarwinds.com

Scott, I ran into an issue on this one that may prove tough to overcome. It looks like custom metrics are based on queries running against the monitored instance. I don't see a way to query against the repo which is where we'd get the data you are looking for from... Hate to say it, but I think I'm stuck on this one.

So if the migration missed that, it begs the question of other potential pitfalls yet to be run into. I agree with the full backup/restore option - safest bet.