SSIS - Package Logging
v2008 SQL, SSIS, For the life of me, I cannot get my package to log output.
Control Flow/Logging, provider type = SSIS log provider for Text files
Configuration is File Connection Mgr; usage type: Create file
file: E:\MSSQL\Log\LogName.txt
exec the package, i write nothing.
I thought maybe it could be better handled w/an event handler, but that, too, isn't working.
This is terribly urgent. can anybody point me in the right direction?
event handler would be fab, but logging itself is fine, too.
i just need a log written upon execution, failure or success. package completion generates a log. easy sneasy, one would think
Control Flow/Logging, provider type = SSIS log provider for Text files
Configuration is File Connection Mgr; usage type: Create file
file: E:\MSSQL\Log\LogName.txt
exec the package, i write nothing.
I thought maybe it could be better handled w/an event handler, but that, too, isn't working.
This is terribly urgent. can anybody point me in the right direction?
event handler would be fab, but logging itself is fine, too.
i just need a log written upon execution, failure or success. package completion generates a log. easy sneasy, one would think
ASKER
Yes, but this is to write to a table. I'd rather write the flat file log. I've enabled logging as in your first jpg, i then added the provider of the text file type, and it presumably uses the flat file connection mgr.
but it's not writing anything.
but it's not writing anything.
ASKER
And i just tried the sql table logging. just as you posted in the jpg's. it, too, didn't write jack. i pointed it to an oledb cxn mgr, yet no sysdtslog table was created.
ASKER
the one thing that puzzles me --- in 'Confiugre SSIS Logs: PackageName' dialog I have two objects in the Containers: section on the left side:
checkbox, PackageName
checkbox, PackageName
The top one is checked, the bottom one isn't. A., I don't know why there are two there, and B., I've tried it with both of them checked, presumably enabling the logging at the package level.
But, up there where i say 'PackageName' --- it's the same package name, just listed twice.
checkbox, PackageName
checkbox, PackageName
The top one is checked, the bottom one isn't. A., I don't know why there are two there, and B., I've tried it with both of them checked, presumably enabling the logging at the package level.
But, up there where i say 'PackageName' --- it's the same package name, just listed twice.
ASKER
i am sorry for being all crazy on this, but it is awfully urgent. do you think i could set the logging within package configurations?
Logging
Event Handler
Package Configurations
Whichever is most ideal, please advise.
Logging
Event Handler
Package Configurations
Whichever is most ideal, please advise.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
the objects underneath your package on the left side, in containers, do not exist under my package.
as i mentioned before, i have my package listed twice
it's just a simple data flow task -- oledb source, flat file destination.
logging.bmp
as i mentioned before, i have my package listed twice
it's just a simple data flow task -- oledb source, flat file destination.
logging.bmp
might be worth checking the permissions on the folder you are trying to write the log to. Should have modify rights. If the package is scheduled you should grant the job agent account rights. If you manually run it should be your account.
ASKER
i'm an admin to everything (sql, shares, the entire box), and everything is defined with sa right now (i know.. i need to change this)
on a side note, the only way i've been able to 'schedule' the pkg is via sql agent. is there another means of doing this from within SSIS ?
but that's not near as important as the logging
on a side note, the only way i've been able to 'schedule' the pkg is via sql agent. is there another means of doing this from within SSIS ?
but that's not near as important as the logging
I will install SQL 2008 in a virtual machine to take a look at your project ... but could you attach it here?!
"on a side note, the only way i've been able to 'schedule' the pkg is via sql agent. is there another means of doing this from within SSIS ?" The standard way is fromo SQL agent
regards,
Pedro
www.pedrocgd.blogspot.com
"on a side note, the only way i've been able to 'schedule' the pkg is via sql agent. is there another means of doing this from within SSIS ?" The standard way is fromo SQL agent
regards,
Pedro
www.pedrocgd.blogspot.com
ASKER
>>but could you attach it here?!
I'm sorry, Pedro, I can't do that. If you've got a less public means of receiving (ie, email), I will be able to do so.
>.The standard way is fromo SQL agent
Cool.
I'm sorry, Pedro, I can't do that. If you've got a less public means of receiving (ie, email), I will be able to do so.
>.The standard way is fromo SQL agent
Cool.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
dbaSQL,
Check my email in my blog and sent it to me... I will take a look during the day!
Regards,
Pedro
www.pedrocgd.blogspot.com
Check my email in my blog and sent it to me... I will take a look during the day!
Regards,
Pedro
www.pedrocgd.blogspot.com
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i will split the points amongst you all and close. i ended up using package configurations. about the 20th gazillionth time into it, it worked. (still got a lot of learning to do with this v2008 SSIS)
thank you each for you time
thank you each for you time
Regards,
Pedro
www.pedrocgd.blogspot.com
SSIS-LoggingProvider1.JPG
SSIS-LoggingProvider2.JPG
SSIS-LoggingProvider3.JPG
SSIS-LoggingProvider4.JPG
SSIS-LoggingProvider5.JPG