dbTalk Databases Forums  

DTS Log Difference

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss DTS Log Difference in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Prabhat
 
Posts: n/a

Default DTS Log Difference - 04-28-2005 , 05:00 AM






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





Reply With Quote
  #2  
Old   
Chandra
 
Posts: n/a

Default RE: DTS Log Difference - 04-28-2005 , 05:16 AM







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:

Quote:
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






Reply With Quote
  #3  
Old   
Prabhat
 
Posts: n/a

Default Re: DTS Log Difference - 04-28-2005 , 06:15 AM



Hi Chandra! Thanks for your reply.

Prabhat


"Chandra" <Chandra (AT) discussions (DOT) microsoft.com> wrote

Quote:
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








Reply With Quote
  #4  
Old   
Chandra
 
Posts: n/a

Default Re: DTS Log Difference - 04-28-2005 , 07:38 AM



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:

Quote:
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









Reply With Quote
  #5  
Old   
Prabhat
 
Posts: n/a

Default Re: DTS Log Difference - 04-28-2005 , 11:23 AM



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

Quote:
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











Reply With Quote
  #6  
Old   
Chandra
 
Posts: n/a

Default Re: DTS Log Difference - 04-29-2005 , 12:50 AM



Hi Prabhat,
I will try to answer your post "DTS - With Conditions".

for more information on rating the post, please refer to
http://www.microsoft.com/wn3/locales....htm#RateAPost

thanks and regards
Chandra


"Prabhat" wrote:

Quote:
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












Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.