[SSIS] Enable 3rd party logging mechanisms to refer to ssisdb.internal.executable_statistics - by Jamie Thomson

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 763236 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 9/18/2012 2:34:28 AM
Access Restriction Public


Whenever an executable is executed it creates a record in [ssisdb].[internal].[executable_statistics] and hence is uniquely identifiable within the execution by [statistics_id]

Often people supplement the information in SSIS Catalog with their own custom logging infrastructure and it would be fantastic if we had a way to tie custom logging activity back to that record in [ssisdb].[internal].[executable_statistics].

Sign in to post a comment.
Posted by Microsoft on 4/1/2014 at 10:34 PM
Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SSIS. The reasons for closing these bugs are following:
1.     The fix is risky to implement in the current version of the product
2.     Scenarios reported in the bug are not common enough
3.     A viable workaround is available.

If the issue is a critical business interruption, please call CSS (Customer Support Services).

Thanks again for reporting the product issue and continued support in improving our product.

Mariusz Cichomski
Program Manager