April 20, 2011 at 5:03 am
[font="Tahoma"][font="Tahoma"]Hello Friends,
I am trying to create a log... The following is my requirement.
I want 2 tables. one to store the package run information and another one to store the details of the errors generated while executing the package.
I tried the inbuilt logging feature with SQL Server option and found that the entries are stored in sysssislog table. Rather i would like these values to be stored in a user defined table.
Similarly i would like to log the errors in a user defined table.
Please help me on this.
Thanks & Regards,
Murali[/font][/font]
April 20, 2011 at 5:35 am
See if this helps: http://www.mssqltips.com/tip.asp?tip=1417
Russel Loski, MCSE Business Intelligence, Data Platform
April 20, 2011 at 7:22 am
[font="Tahoma"]
Hello Russell,
Thanks for your reply. I went through the blog mentioed by you. However, i just want to know if there is a way to store the package run information without explicitly using Execute SQL Task.
As i had mentioned, i would like to know if there is a way to capture these information during the end of the package execution.
[/font]
April 21, 2011 at 4:16 am
Hello
Never tried this but maybe you can check if an INSERT/UPDATE trigger on the sysssislog table will do the job for you?
Also, maybe at the end of your package, you can just call one sp which will select/group data from the sysssislog table and perform the neccessary INSERTS/UPDATES to your table
Regards
Regards
Brian Ellul
----------------------------------------------------------------------------------
Computers are incredibly fast, accurate, and stupid. Human beings are incredibly slow, inaccurate, and brilliant. Together they are powerful beyond imagination.
- Albert Einstein -
April 21, 2011 at 6:45 am
You can't log to a custom table with the built-in log provider.
You can set up custom logging using Execute SQL Tasks and Event Handlers.
As mentioned before in this thread, you can also parse the system log table using either stored procedures or triggers, but that creates extra overhead of course.
Maybe the best option is to create some views on top of the log table?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
April 21, 2011 at 6:48 am
[font="Tahoma"]
Thanks Brian and Koen for your replies. I created a user defined table and added entries to those tables through [sp_ssis_addlogentry] sp which got created after enabling Logging through SQL Server.
I updated the SP mentioned above and added statement to insert the package status.
[/font]
April 25, 2011 at 12:11 pm
Same thing here...
Use BI xPress
http://pragmaticworks.com/Products/Business-Intelligence/BIxPress/Overview.aspx
Jacob Milter
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply