Help get this topic noticed by sharing it on Twitter, Facebook, or email.

Duplicated SPName values in DBAmp_Log causing invalid joins for Performance views

We just installed the most recent update to take advantage of the performance package. It appears to be working well for the most part, but we are seeing some odd behavior in the pre-built _Perf views.

Looking at the SQL, they appear to be doing joins on SPName in the DBAmp_Log table, but we have more than one job instance being given the same SPName value, so it is throwing off the performance numbers (large negative run times).
1 person has
this problem