Dbo.sysdtslog90
Dec 4, 2007Hi,
is there any way to use dbo.sysdtslog90 table for SSIS package logging?
ADVERTISEMENT
Improvement Sysdtslog90?
Apr 12, 2007hello
im trying to create a ssis monitoring tool (using sysdtslog90, reporting services and system tables) including sql server agent ssis schedules/history. but im having some problems evaluating sysdtslog90. im using the built in SSIS logging without any custom logging tasks (i only log OnError and OnWarning) to keep the logging table as small as possible (one sysdtslog90 table for all packages running on the server).
and there is the problem:
there are some executions without any events except OnError. the source of this event is the name of the failed task, so how do i get the name and id of the failed package?
"normal" executions have "PackageStart" and "PackageEnd" where the sourceid and source are equal with the id and name of the package
i could add logging for OnPreValidate and catch the first line, because no package can fail before validation!?
but isnt there any better solution?
i would love it to have two more columns in sysdtslog90.. package id and name. would be much easier to evaluate sysdtslog90 :/
- paul
How Link Executionid Of Sysdtslog90
Oct 30, 2006I have enabled logging using database.
When I try to query the sysdtslog90 table using System::ExecutionInstanceGUID to link executionid - it is not matching.
Any resolution?
Thanks
Meaning Of Datacode In Sysdtslog90?
Jun 13, 2006The documentation says:
"An integer value that identifies the event associated with the log entry. The value 0 indicates the event provided no identifier."
When I look at the sysdtslog90 table and I filter for 'PackageEnd' events, I see a value of 0, 1 or 3 in the datacode column. Is there any information I can glean from these values, e.g. package success or failure?
Sysdtslog90 Table Creation Issue
Jul 25, 2007Hi,
when I select sql server provider pointing to connection mydatabase for Logging the sysdtslog90 table is not getting created. However if I point the connection to msdb - sysdtslog90 it works fine.
Can I have sysdtslog90 under the application database? what are the steps to do this?
Thanks in advance.
Prabhakaran
Log Data Wrongly Redirected To Master.dbo.sysdtslog90
Aug 20, 2007
I have been using the SSIS Log Provider for SQL Server quite a lot this year with little to no problems. Recently however as I edit or create packages the logging seems to keep going to the master.dbo.sysdtslog90 table as opposed to the [db].dbo.sysdtslog90 as setup in the package. I tried totally deleting the connection from the package and recreating and still had the problem.
Is there some setting on the SQL server itself that can cause this? Our "dba" likes to make changes without letting anyone know about them.
Any ideas?
Sysdtslog90, Message Field And My Unicode Ignorance
Feb 5, 2008Sorry to be an ignorant American here, but I'm having a challenge I just can't seem to wrap my head around.
I am attempting to make a nice query for a report that will show how our SSIS jobs are doing. All my packages use the native SQL Server logging capability. The table is sysdtslog90 and it stores the message to a field called 'message' (crazy, I know) with a datatype of nvarchar(4096).
The challenge I'm having is that I'd like to grab all lines where my message is X. The following queries will return no results. The first is me typing in the message I see in the window, the second is copying the value and pasting it in. I know there are instances where that message exists, sadly, in the log table.
Code Snippet
SELECT
L.*
FROM
sysdtslog90 L
WHERE
L.message = N'A commit failed.'
SELECT
L.*
FROM
sysdtslog90 L
WHERE
L.message = N'A commit failed. '
If I were to change that clause out to a like, it'd work just fine. Is that the appropriate way to work with unicode literals? It doesn't feel right.
Code Snippet
SELECT
L.*
FROM
sysdtslog90 L
WHERE
L.message LIKE N'A commit failed.%'
I have exported my sysdtslog90 table to a unicode flat file and looked at this message in a hex editor and it looks fine, nothing looked awry. I then opened the file up in SSMS, thinking perhaps it's a silent conversion issue with pasting, but to no avail. Anyone have some guidance for me?
Logging Package Name For Any Event In Sysdtslog90 Logging Table
Oct 17, 2007
Hi,
I decided to use the SQL Server log provider to store logging data of all my Integration Services packages. I also created some reports about this data for operating purposes.
I have a problem occurs the name of the executing package is not always written to the log,but the name of the single task which failed. But that is not very useful information for operating, because I do not see any chance to get the name of the package by the information which is logged in the sysdtslog90 table in the database which I defined for SSIS Logging.
How do I configure the package to always log the package information into the table, too?
Best regards,
Stefoon