I suggest you ...

Best Practices Analyzer - Customize Export

When you export the results of the Best Practice Analyzer it only includes column for "Severity", "Name" and "Path". This doesn't tell you important pieces of information like the name of the project that is affected, the name of the package that is affected or the name of the best practice that was violated. Without that info, the export is pretty much useless.

44 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Adam Hafner shared this idea  ·   ·  Admin →
    planned  ·  AdminPragmatic Works (Admin, Pragmatic Works) responded  · 

    In the 2017.4 release, the Best Practices Result Export now includes the rule that was violated and the recommendation. The path value reflects what object (package, task, component) violated the rule.
    We are still in process on adding the root item to the export, but this should be included in the next release. The root item is the starting point for the scan, and could be a specific package, a project, a database, or an entire SQL Server.

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Per Hjorth Pedesen commented  · 

        I found using the tables [dbo.BestPracticesResults] and [dbo.BestPracticesRules] more useful because we also have to add additional information to the result. E.g. Author for distribution of violated objects.

      Feedback and Knowledge Base