Do you mean you don't want to set up another SQL Server instance for the DPA repo or ?
Not sure what you are asking, but in general, the reason we don't recommend registering the instance holding the repo for monitoring is that's where we do our heavy lifting. You can certainly do so, but you will see a lot of activity of our normal processing. It will also monitor the other databases as well though and is technically feasible.
OK, yep, you can do that. Let me know if you don't want to see the repo activity as there's a way to add to the our collection query to exclude things.
Basically, each target entered into DPA to be monitored requires a license.
If this is to troubleshoot performance issues, you can submit a support case and they likely can kick you a temp license while troubleshooting.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.