![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi All, I use the DTSRUN utility with /L option to provide the log filename with path for logging. I think in Package property "Error File" option is same as the above but there the NAME will be given in design time. Also there is an option to log to SQL Server - MSDB and also to eventlog. Which method is the best for ERROR Log? Can any one explain with detail or any website link that explain all that? Thanks Prabhat |
#3
| |||
| |||
|
|
It depends on who require the data. if the data is being used my Network/System Administrators then you can log it into Event Log. If Database Administrators are going to use the data then u log it on MSDB. If the data is required by the Application Suport Team the u can log it into a flat file or one of the tables in the Production Database. Where ever you log the data its one and the same. hope this answers the question. thanks and regards Chandra "Prabhat" wrote: Hi All, I use the DTSRUN utility with /L option to provide the log filename with path for logging. I think in Package property "Error File" option is same as the above but there the NAME will be given in design time. Also there is an option to log to SQL Server - MSDB and also to eventlog. Which method is the best for ERROR Log? Can any one explain with detail or any website link that explain all that? Thanks Prabhat |
#4
| |||
| |||
|
|
Hi Chandra! Thanks for your reply. Prabhat "Chandra" <Chandra (AT) discussions (DOT) microsoft.com> wrote in message news:8EF7A0BC-4391-40C0-A9FB-26A46DF9E14F (AT) microsoft (DOT) com... It depends on who require the data. if the data is being used my Network/System Administrators then you can log it into Event Log. If Database Administrators are going to use the data then u log it on MSDB. If the data is required by the Application Suport Team the u can log it into a flat file or one of the tables in the Production Database. Where ever you log the data its one and the same. hope this answers the question. thanks and regards Chandra "Prabhat" wrote: Hi All, I use the DTSRUN utility with /L option to provide the log filename with path for logging. I think in Package property "Error File" option is same as the above but there the NAME will be given in design time. Also there is an option to log to SQL Server - MSDB and also to eventlog. Which method is the best for ERROR Log? Can any one explain with detail or any website link that explain all that? Thanks Prabhat |
#5
| |||
| |||
|
|
Good to know that the solution addressed your needs. Really appreciate if you can rate the Post. This can be done by answering "Was this post helpful to you?" "Prabhat" wrote: Hi Chandra! Thanks for your reply. Prabhat "Chandra" <Chandra (AT) discussions (DOT) microsoft.com> wrote in message news:8EF7A0BC-4391-40C0-A9FB-26A46DF9E14F (AT) microsoft (DOT) com... It depends on who require the data. if the data is being used my Network/System Administrators then you can log it into Event Log. If Database Administrators are going to use the data then u log it on MSDB. If the data is required by the Application Suport Team the u can log it into a flat file or one of the tables in the Production Database. Where ever you log the data its one and the same. hope this answers the question. thanks and regards Chandra "Prabhat" wrote: Hi All, I use the DTSRUN utility with /L option to provide the log filename with path for logging. I think in Package property "Error File" option is same as the above but there the NAME will be given in design time. Also there is an option to log to SQL Server - MSDB and also to eventlog. Which method is the best for ERROR Log? Can any one explain with detail or any website link that explain all that? Thanks Prabhat |
#6
| |||
| |||
|
|
Hi Chandra, Yes This Post was answered my question and Helpful to me. Thanks. Can U please look into my Post "DTS - With Conditions" and Help me in that? Thanks Prabhat "Chandra" <Chandra (AT) discussions (DOT) microsoft.com> wrote in message news:B1BF847C-25D8-44FE-B082-77D8687FBE0F (AT) microsoft (DOT) com... Good to know that the solution addressed your needs. Really appreciate if you can rate the Post. This can be done by answering "Was this post helpful to you?" "Prabhat" wrote: Hi Chandra! Thanks for your reply. Prabhat "Chandra" <Chandra (AT) discussions (DOT) microsoft.com> wrote in message news:8EF7A0BC-4391-40C0-A9FB-26A46DF9E14F (AT) microsoft (DOT) com... It depends on who require the data. if the data is being used my Network/System Administrators then you can log it into Event Log. If Database Administrators are going to use the data then u log it on MSDB. If the data is required by the Application Suport Team the u can log it into a flat file or one of the tables in the Production Database. Where ever you log the data its one and the same. hope this answers the question. thanks and regards Chandra "Prabhat" wrote: Hi All, I use the DTSRUN utility with /L option to provide the log filename with path for logging. I think in Package property "Error File" option is same as the above but there the NAME will be given in design time. Also there is an option to log to SQL Server - MSDB and also to eventlog. Which method is the best for ERROR Log? Can any one explain with detail or any website link that explain all that? Thanks Prabhat |
![]() |
| Thread Tools | |
| Display Modes | |
| |