athornbury1

Comments

  • Though probably not officially supported and a bit of a hassle, this can be done directly in the backed database. The NAME field in the CON_SQL_NAME table allows up to 100 characters. Be advised, this may alter the appearance or layout of forms in DPA. Also restarting, this is most likely NOT supported. - In DPA, identify…
    in Increase SQL Name Length Comment by athornbury1 August 2019
  • I face the same problem where i have a large number of very similar databases (10,000+) spread across 7 SQL Server instances. There are many times when the same HASH is calculated for completely different SQL statements on different monitored instances. Thus I can only name so many of the HASHes until I run into a…
    in Improve Query Naming with Group , Automation, Less rules Comment by athornbury1 September 2019
  • I added a custom metrics to accomplish this. See my post here:TempDB
    in tempdb Monitoring Comment by athornbury1 August 2019
  • Updated this code to something that is usable to initially create a unique HASH/NAME list and to maintain said list over time. Basically collect all of the HASHes from the CON_STATS_...X and CONST_X tables to find a list of everything. Whittle it down from there to only contain HASH numbers that appear once in the entire…
    in Improve Query Naming with Group , Automation, Less rules Comment by athornbury1 October 2019
  • jsql- sorry for the long delay, I was not actively monitoring thwack. The tempdb stuff I created is a set of Custom Metrics; it was not built-in to DPA at the time. I’m no longer at a company that uses DPA but a colleague indicated that the newest version of DPA may have taken these ideas and incorporated it into the…
    in TempDB Monitoring and Troubleshooting: Out of Space Comment by athornbury1 June 2021
Avatar