Post reply

ssis logging incomplete

  • October 13, 2009 at 1:09 am

    #385565

    Hi,

    I have created a package and enabled logging on sql2008. when run in BIDS, it creates the sysssislog table in the specified database and logs all events I have checked in the logging options.

    after this I uploaded it into the ssis repository and created a job in the sql server agent. when i run the same package through this job, the log lines are incomplete. the are missing lines for the tasks.

    I enabled logging by checking just the first checkbox, so that all child elements in the package should inherit the logging settings. I think the sql server agent does not work correctly with the inherited log settings.

    Can someone reproduce this issue?

    here are the steps how to do this in just 5 minutes:

    - create a new ssis package

    - create one or better two simple tasks (SQL Task, statement "select 1")

    - go in the menu to "SSIS"-"logging"

    - check the first checkbox in the treeview

    - add a new log provider for sql server and choose a database

    - go in the details tab and click onPreExecute and onPostExecute

    - run the package

    => a system table will be created in the chosen database with name "sysssislog"

    => check the contents, it should be at least 4 lines for the package and 2 lines for each task

    - open SSMS

    - connect to ssis and upload the package

    - connect to sql server and add a job for the uploaded task

    - run the job

    - check the syssslog-table

    => the result should be incomplete now

    I have reproduced this on 2 machines, both running on win2003srv and sql2008.

    It would help me a lot if anyone could confirm this issue.

    thank you!

  • October 23, 2009 at 1:19 am

    #1069826

    can someone confirm this please?

    I still have no solution and get no feedback from microsoft 🙁

  • May 2, 2011 at 11:20 am

    #1318578

    See this very good article about custom ssis logging

    http://pragmaticworks.com/Products/Business-Intelligence/BIxPress/ssis-logging-auditing-monitoring.aspx

  • May 2, 2011 at 11:03 pm

    #1318866

    Thanks for your answer.

    I got a solution for my problem some time ago.

    The Problem was a bug in SQL 2008.

    A Hotfix and a workaround can be found here:

    http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/511502a6-99d6-4693-94da-2c317c3f59c6

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply