Konesans File Watcher Tasks

Hello All

Just curious if there are any tutorials/help files/forums on using this and other Konesans control Flow and data flow task? most import the flow watcher task.

thanks

Karen

No is the honest answer. We write the documentation pages on the SQLIS site for each component, but as free components we have not gone that far on documentation. Questions pop up here about them or you can contact us direct (http://www.konesans.com/contact.aspx), we are happy to help.

keeping TRN files

Hello All,
I was wondering if anyone has some 'general rules' on how long they hold on
to TRN files?
thanks...
In a production environment this'll depend on the SLA, if mention is made of
a historical point-in-time recovery and the frequency of tape backups etc.
For my part, I keep all the logs inbetween the last 2 full database backups
and the log directory and database directory are both backed up to tape
which is maintained by a service provider, so in a sense, all logs are held
on to. For the development environment we use simple recovery mode and full
backups only, in agreement with all parties involved that sourcesafe is used
for programming object modifications.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com.
|||I keep them as long as possible. If a backup fails you can restore from the
last successful backup (which could be months ago) and apply all the
transaction logs up to the present. So its a way of backing up your backup -
double protection.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"MSUTech" <MSUTech@.discussions.microsoft.com> wrote in message
news:211D0D77-5668-4E0C-A105-64CA2A802D9F@.microsoft.com...
> Hello All,
> I was wondering if anyone has some 'general rules' on how long they hold
> on
> to TRN files?
> thanks...

keeping TRN files

Hello All,
I was wondering if anyone has some 'general rules' on how long they hold on
to TRN files?
thanks...In a production environment this'll depend on the SLA, if mention is made of
a historical point-in-time recovery and the frequency of tape backups etc.
For my part, I keep all the logs inbetween the last 2 full database backups
and the log directory and database directory are both backed up to tape
which is maintained by a service provider, so in a sense, all logs are held
on to. For the development environment we use simple recovery mode and full
backups only, in agreement with all parties involved that sourcesafe is used
for programming object modifications.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com.|||I keep them as long as possible. If a backup fails you can restore from the
last successful backup (which could be months ago) and apply all the
transaction logs up to the present. So its a way of backing up your backup -
double protection.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"MSUTech" <MSUTech@.discussions.microsoft.com> wrote in message
news:211D0D77-5668-4E0C-A105-64CA2A802D9F@.microsoft.com...
> Hello All,
> I was wondering if anyone has some 'general rules' on how long they hold
> on
> to TRN files?
> thanks...

keeping TRN files

Hello All,
I was wondering if anyone has some 'general rules' on how long they hold on
to TRN files?
thanks...In a production environment this'll depend on the SLA, if mention is made of
a historical point-in-time recovery and the frequency of tape backups etc.
For my part, I keep all the logs inbetween the last 2 full database backups
and the log directory and database directory are both backed up to tape
which is maintained by a service provider, so in a sense, all logs are held
on to. For the development environment we use simple recovery mode and full
backups only, in agreement with all parties involved that sourcesafe is used
for programming object modifications.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com.|||I keep them as long as possible. If a backup fails you can restore from the
last successful backup (which could be months ago) and apply all the
transaction logs up to the present. So its a way of backing up your backup -
double protection.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"MSUTech" <MSUTech@.discussions.microsoft.com> wrote in message
news:211D0D77-5668-4E0C-A105-64CA2A802D9F@.microsoft.com...
> Hello All,
> I was wondering if anyone has some 'general rules' on how long they hold
> on
> to TRN files?
> thanks...

Keep backup files ?

We are running SQL Server 2000.
We would like to know:
Is it possible to make ad hoc backup of the production
database in the same directory where daily database backup
is generated by the Database Maintenance Plan ? We have
selected "Daily backup is 'Remove files older than 1 week'
option is chosen for the production database" in the
Database Maintenance Plan.
This is because if the "Database Maintenance Plan" only
remove backups generated by itself, it is perfect for us
to put ad hoc backup there as we don't want to create
another directory for holding ad hoc backup.
ThanksYes you can place manually run backup files in the same directory as the
maintenance plan stores them. In fact, some use this method to run restore
jobs to a secondary database as you don't have to write a script to
determine the latest backup generated from the maintenance plan.
HTH
--
Ray Higdon MCSE, MCDBA, CCNA
--
"Roger Lee" <anonymous@.discussions.microsoft.com> wrote in message
news:02b701c3a195$11bdb430$a501280a@.phx.gbl...
> We are running SQL Server 2000.
> We would like to know:
> Is it possible to make ad hoc backup of the production
> database in the same directory where daily database backup
> is generated by the Database Maintenance Plan ? We have
> selected "Daily backup is 'Remove files older than 1 week'
> option is chosen for the production database" in the
> Database Maintenance Plan.
> This is because if the "Database Maintenance Plan" only
> remove backups generated by itself, it is perfect for us
> to put ad hoc backup there as we don't want to create
> another directory for holding ad hoc backup.
> Thanks