Showing posts with label logging. Show all posts
Showing posts with label logging. Show all posts

Monday, March 19, 2012

DTS Package Logging - can u limit it?

Hello. When you turn Logging on, for a DTS package, it
appears to save the history forever? If that's true, is
there an option to clear DTS package logs, after like 30
days? or would you need to write something to do this
purge manually? THanks, BruceYou can delete all the logs for a package from the Package Properties,
Logging tab.
You can also right click on local packages under the DTS node in
Enterprise Manager and select Logging. From here you have a bit more
control on selecting packages, selecting logs to delete, etc.
If you want to automate this somehow, you could code your own
maintenance of these using the DTS Object Model and schedule this
through a job. Take a look at the RemovePackageLogRecords method of
the PackageSQLServer object.
-Sue
On Fri, 29 Oct 2004 10:23:48 -0700, "Bruce de Freitas"
<bruce@.defreitas.com> wrote:

>Hello. When you turn Logging on, for a DTS package, it
>appears to save the history forever? If that's true, is
>there an option to clear DTS package logs, after like 30
>days? or would you need to write something to do this
>purge manually? THanks, Bruce|||THanks Sue. Yes, I was looking for an option hopefully
built-in to SQL Server, to give me a set number of logs,
or a set number of days, like you can adjust the number of
SQL error log files. Yep, I'll check out the homegrown
approach... THanks, Bruce

>--Original Message--
>You can delete all the logs for a package from the
Package Properties,
>Logging tab.
>You can also right click on local packages under the DTS
node in
>Enterprise Manager and select Logging. From here you have
a bit more
>control on selecting packages, selecting logs to delete,
etc.
>If you want to automate this somehow, you could code your
own
>maintenance of these using the DTS Object Model and
schedule this
>through a job. Take a look at the
RemovePackageLogRecords method of
>the PackageSQLServer object.
>-Sue
>On Fri, 29 Oct 2004 10:23:48 -0700, "Bruce de Freitas"
><bruce@.defreitas.com> wrote:
>
>.
>

DTS Package Logging - can u limit it?

Hello. When you turn Logging on, for a DTS package, it
appears to save the history forever? If that's true, is
there an option to clear DTS package logs, after like 30
days? or would you need to write something to do this
purge manually? THanks, Bruce
You can delete all the logs for a package from the Package Properties,
Logging tab.
You can also right click on local packages under the DTS node in
Enterprise Manager and select Logging. From here you have a bit more
control on selecting packages, selecting logs to delete, etc.
If you want to automate this somehow, you could code your own
maintenance of these using the DTS Object Model and schedule this
through a job. Take a look at the RemovePackageLogRecords method of
the PackageSQLServer object.
-Sue
On Fri, 29 Oct 2004 10:23:48 -0700, "Bruce de Freitas"
<bruce@.defreitas.com> wrote:

>Hello. When you turn Logging on, for a DTS package, it
>appears to save the history forever? If that's true, is
>there an option to clear DTS package logs, after like 30
>days? or would you need to write something to do this
>purge manually? THanks, Bruce
|||THanks Sue. Yes, I was looking for an option hopefully
built-in to SQL Server, to give me a set number of logs,
or a set number of days, like you can adjust the number of
SQL error log files. Yep, I'll check out the homegrown
approach... THanks, Bruce

>--Original Message--
>You can delete all the logs for a package from the
Package Properties,
>Logging tab.
>You can also right click on local packages under the DTS
node in
>Enterprise Manager and select Logging. From here you have
a bit more
>control on selecting packages, selecting logs to delete,
etc.
>If you want to automate this somehow, you could code your
own
>maintenance of these using the DTS Object Model and
schedule this
>through a job. Take a look at the
RemovePackageLogRecords method of
>the PackageSQLServer object.
>-Sue
>On Fri, 29 Oct 2004 10:23:48 -0700, "Bruce de Freitas"
><bruce@.defreitas.com> wrote:
>
>.
>

DTS Package Logging - can u limit it?

Hello. When you turn Logging on, for a DTS package, it
appears to save the history forever? If that's true, is
there an option to clear DTS package logs, after like 30
days? or would you need to write something to do this
purge manually? THanks, BruceYou can delete all the logs for a package from the Package Properties,
Logging tab.
You can also right click on local packages under the DTS node in
Enterprise Manager and select Logging. From here you have a bit more
control on selecting packages, selecting logs to delete, etc.
If you want to automate this somehow, you could code your own
maintenance of these using the DTS Object Model and schedule this
through a job. Take a look at the RemovePackageLogRecords method of
the PackageSQLServer object.
-Sue
On Fri, 29 Oct 2004 10:23:48 -0700, "Bruce de Freitas"
<bruce@.defreitas.com> wrote:
>Hello. When you turn Logging on, for a DTS package, it
>appears to save the history forever? If that's true, is
>there an option to clear DTS package logs, after like 30
>days? or would you need to write something to do this
>purge manually? THanks, Bruce|||THanks Sue. Yes, I was looking for an option hopefully
built-in to SQL Server, to give me a set number of logs,
or a set number of days, like you can adjust the number of
SQL error log files. Yep, I'll check out the homegrown
approach... THanks, Bruce
>--Original Message--
>You can delete all the logs for a package from the
Package Properties,
>Logging tab.
>You can also right click on local packages under the DTS
node in
>Enterprise Manager and select Logging. From here you have
a bit more
>control on selecting packages, selecting logs to delete,
etc.
>If you want to automate this somehow, you could code your
own
>maintenance of these using the DTS Object Model and
schedule this
>through a job. Take a look at the
RemovePackageLogRecords method of
>the PackageSQLServer object.
>-Sue
>On Fri, 29 Oct 2004 10:23:48 -0700, "Bruce de Freitas"
><bruce@.defreitas.com> wrote:
>>Hello. When you turn Logging on, for a DTS package, it
>>appears to save the history forever? If that's true, is
>>there an option to clear DTS package logs, after like 30
>>days? or would you need to write something to do this
>>purge manually? THanks, Bruce
>.
>

Sunday, February 26, 2012

DTS logging in SQL server 2000

Can you plz tel me where all dts information store in sql server 2000.

is it in the master databse in some table

thanks

sandipan

You should try this group for DTS information:

http://groups.google.com/group/microsoft.public.sqlserver.dts?lnk=srg

If you are saving the DTS packages to the database, they are stored in msdb.

DTS Log Difference

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
PrabhatIt 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 Databas
e
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
>
>
>|||Hi Chandra! Thanks for your reply.
Prabhat
"Chandra" <Chandra@.discussions.microsoft.com> wrote in message
news:8EF7A0BC-4391-40C0-A9FB-26A46DF9E14F@.microsoft.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:
>
eventlog.
or|||Good to know that the solution addressed your needs. Really appreciate if yo
u
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@.discussions.microsoft.com> wrote in message
> news:8EF7A0BC-4391-40C0-A9FB-26A46DF9E14F@.microsoft.com...
> Database
> into
> eventlog.
> or
>
>|||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@.discussions.microsoft.com> wrote in message
news:B1BF847C-25D8-44FE-B082-77D8687FBE0F@.microsoft.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:
>
it
with
but
detail|||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/locale...s.htm#RateAPost
thanks and regards
Chandra
"Prabhat" wrote:

> 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@.discussions.microsoft.com> wrote in message
> news:B1BF847C-25D8-44FE-B082-77D8687FBE0F@.microsoft.com...
> you
> it
> with
> but
> detail
>
>