aiglee.castillo

mandevil, how do I get access to the Beta? Do I need to do anything in specific? Thanks

Awesome! Thanks! Now I just need to be authorized to download the beta

We are running Windows. If you can send me the workaround that would be great! Thanks.

Also, it's an Azure DB, not sure if that makes a difference. Thanks

Those charts are the ones I got from current - Long running queries - click on hash, pop up - click on historical charts. Database Performance Analyzer 11.1.457

Can't access the Beta, it says unauthorized Let me check where we could do a second installation then, as I imagine having both DPA installations in the same server would not be possible/easy.

Awesome! Thank you for all the information. I think we are really tending to DPA Central, just need to confirm resourcing in general. The idea now is that since we are going to continue to grow, instead of just using the "moved" instance as history, we would keep both active and be able to just keep growing. Thank you!

Awesome, thank you! I looked but couldn't find it.

Fair enough. Thanks for letting me know.

Thanks for the options! Regarding DPA Central, can it be done by still moving the on-premise DPA to Azure but have 2 separate Azure repositories? I read that DPA central uses the server information to connect so I dont know if we can have the 2 DPA instances in one server and connect them through DPA Central.

I don't see the query in trends because its still way faster than my top ones in the trend chart. I can only see it in current. Either way both current and trend queries show only these 2 graphs related to time. These charts are actually for one of the queries that is taking less than 20 microseconds avg over time…

oh, that's awesome, thank you! I have upvoted the request to not select any instance for repository requests. Also, didn't know I could change the alert options in the settings. That's great! Thanks

I don't want to move the repository or keep history. This particular need is because we have DPA installed for different clients in different boxes. We want to be able to export all common settings from one client installation to import in a different client installation and reduce the effort to configure every new client.

Thank you Fabian, Yeah, I saw that article and thought it might not be an option, but if we tell the client what permissions to create and restrict them to the one DB then maybe it would help. I knew it was a long shot, but seems like it might be impossible.

The query already groups by indexes so the number returned is the number of accesses (both reads and inserts). I like your idea and would be good if we are looking to keep historical data. For now I implemented it the dirty way and did do an information alert that will not get triggered (or email me every week with the…