mandevil · Product Manager · ✭✭✭✭✭

What you can do is shutdown the DPA server that you know of and then look at the repo connections. If you see the schema owner sessions still, note the machine they are coming from and shutdown that DPA server before starting up the new one.

Assuming you have access to the repo... Step 1: Do a "select id, name from cond" -- note the newly added instances by ID. Step 2: update the options for one of the newly added instances (again, note which ID got updated) Step 3: Do a "select * from condprm where id = <id>" -- <id> being the number from step 2. This should…

This one may take a little poking around (likely need to look at a few things). Also, can you check to see if any backups or dbcc checkdb kinds of jobs are scheduled for during the time frame this occurred? I think at this point, a screen share would be best. Have you engaged support to help read the tea leaves? I could…

Hey Dave, do you know who your account rep is? They should be able to facilitate this for you. Also, are you talking Azure SQL Databases? If so, yes, there is a license for those - something you rep can answer also. Just remember, you can monitor Azure SQL DB with either a cat 1 or a cat 2 license if you have one…

OK, gentle it is. 8 ) For freespace, you have to kind of think in reverse. Also, you don't have to fill in all of the threshold levels. My recommendation is to set the following values: High: min(0), max(10) Medium: min(10), max(20) Run a test on the alert against the one with low space and make sure it triggers. After…

We currently don't have reports for resource metrics. However, there is a feature request to build that functionality out: Please vote that feature up as it will help get PM attention for a future release...

I'd recommend you check out this custom report (query against the repo): Custom Report - Blocking Report If not exactly the output you want, it's a great place to start to get the blocking data out of the repo.

Are you meaning to capture this real-time while something is in flight? Like running SP_WHO2? Have you looked at the view historical charts view? Does that help? You can also query our summary tables for execution count (con_stats_sum_<ID>) where id is from select id, name from cond -- where name is the monitored instance…

CLEAN_DAYS_OF_DETAIL option should allow for you to extend the number of days kept. Keep in mind this will only effect the wait based data (not resource metric retention). If you change it for a specific database instance, it will not take effect until the next time the cleaner runs (nightly). When the cleaner job kicks…

Great question. We definitely strive to be as transparent as possible with what's required. All of this is publicly consumable in our KB system: Oracle: SolarWinds Knowledge Base :: Oracle Permissions for DPA Monitoring SQL Server: SolarWinds Knowledge Base :: SQL Server Permissions for DPA Monitoring Sybase: SolarWinds…

You can currently set alert blackouts, but the only way I know of at an aggregate scale would be to update COND directly with a scheduled script. If you look at the COND table in your repo, you'll see a couple columns - command and status. You can update the command to 'STOP' or 'START' as you desire which will turn off…

You could set something up as a boolean type of query. Check out using like a CASE statement in your select to determine changes and then alert based on that value.

Can you share what error you are getting in your auth.log? <install_dir>/iwd/tomcat/logs This may have to turn into a support case as it may get involved.

Any performance counters we've collected are persisted in our repo. You should be able to restart the DPA service and all collected data will display. Can you identify exactly what is resetting in your environment? Specific examples?

I think what you are seeing is a flattening of the curve due to averaging. When you zoom out to a month, it will tend to knock off the peaks and fill in the valleys a bit. This is by design though - would you rather show max/peak rather than avg? Regarding resource reports - they don't exist yet. It's something that has…

Generally speaking, in the absence of any other memory pressure, a low procedure cache hit ratio means that when the DBMS goes to see if that statement has run previously and doesn't need to be parsed again, it doesn't find it in cache. This places more overhead on the DBMS because it then has to parse the statement,…

Navigate to C:\Program Files (x86)\Confio\ignite_9\iwc\tomcat\ignite_config\iwc\analysis or the equivalent path where you installed DPA. Uncomment and edit this line: #problem.sql.minimumNumberSql=5 to the number you want to see in the advisors tab.

dmv091, Orion is the framework or core products like NPM. Would you mind posting this question under that product? I just want to make sure you get the best answer possible... Let me know. Thanks!

As long as you are a customer, we can share the ERD (data model) with you. Do you mind submitting a ticket and we'll work with you from there?

We track by SQL statements, but trap the sproc it's running within. Perhaps the easiest way to check is to query the repo directly. First run this query to get the ID of the instance in question: select id, name from COND. Next run this: select h, st, pname from const_<id from first query> where pname = '<name of sproc'

I can certainly pass this on to our program manager regarding the comprehensive guide. Regarding sessions, think SPIDs. Since there isn't a guide at this point, you can certainly submit a case to support and we can do a tutorial and hopefully address any ambiguity for you.

In my Trend view, see the auto-annotation of when a failover occurs for your AGs. You'll see a similar notation within your environment. You can also set up an alert to notify you when a failover happens. Then you can also look at alert history to see when those events occurred.

Currently, we use an open source jTDS driver. This is a limitation on how SQL Server queries the protocol version. We are using the latest jTDS driver with some of our own contributions. Don't believe everything you see. 8 ) Here's a short discussion about this: jTDS - SQL Server and Sybase JDBC driver / Discussion /…

Try going into options -> update connection info. Walk through the wizard making sure everything is correct to monitor the new server. If you are not on DPA 10.0, you may want to upgrade as there was a known issue monitoring 2012 cu7 and above due to a change in the way MS was reporting version.

We are approaching this from two different vantage points, so they can be very different. Host Max Disk Latency = We're asking VMware for the high water mark for disk latency as it sees it - if high, this can cause more systemic issues for anything dependent on those datastores/storage. SQL Latency = We ask SQL over the…

Have you tried this custom alert? Custom Alert - Long Running Queries The minimum interval is 60 seconds, so I don't think we can get down to the 15 seconds you want, but it's close...

Not necessarily. The licenses are for the monitored instances, not the repo or DPA app. With version 9.0 and above, we now have true floating licenses. What this means to you is that if your DPA app is installed on shared files (that failover when the cluster fails over), and starts up on the failover node pointing to the…

First of all, it's great you found the success center article! Seems like your environment is pretty straight forward. Just a few things to remember: * Take a backup * Take a backup * Take a backup 8 ) Everything should work great per the instructions. With a backup though, in case anything does go south, support will be…

Samuel, the scalability will depend on a few different variable. How many overall instances will you be monitoring? How active are your instances? Are you planning on hosting the application server and repo on the same host or separating them? How much resources will the host(s) have? As a rule of thumb, you can monitor…

If you are talking the report, unfortunately there is not an exclude option. You'd have to explicitly do a custom hash list excluding the ones you don't want... If you are talking the trend screen, you can click on the hash value on the right hand side of the chart and there should be an exclude check box so it won't show…