| Author |
Scheduling a script
|
|
| Myth of Sisyphus\). 2005-07-27, 8:23 pm |
| I wish to run this script daily. Can this be scheduled?
backup log shipmateDB with truncate_only
G
| |
| Mike Epprecht \(SQL MVP\) 2005-07-27, 8:23 pm |
| Hi
Look at SQL Server Agent in BOL. It can schedule jobs and run code.
Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Myth of Sisyphus)." <teller_117@hotmail.com> wrote in message
news:iqRFe.4700$q23.748061@news20.bellglobal.com...
>I wish to run this script daily. Can this be scheduled?
>
>
> backup log shipmateDB with truncate_only
>
>
> G
>
>
| |
| Greg D. Moore \(Strider\) 2005-07-27, 8:23 pm |
|
"Mike Epprecht (SQL MVP)" <mike@epprecht.net> wrote in message
news:42e7ed30$1_1@ne
ws.bluewin.ch...
> Hi
>
> Look at SQL Server Agent in BOL. It can schedule jobs and run code.
>
Can I add though that this script is probably not a good idea.
Either run the database in simple mode or perform actual log backups.
> Regards
> --------------------------------
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
>
> IM: mike@epprecht.net
>
> MVP Program: http://www.microsoft.com/mvp
>
> Blog: http://www.msmvps.com/epprecht/
>
> "Myth of Sisyphus)." <teller_117@hotmail.com> wrote in message
> news:iqRFe.4700$q23.748061@news20.bellglobal.com...
>
>
| |
| Myth of Sisyphus\). 2005-07-28, 9:24 am |
| Hi Greg,
I do have a log file backup scheduled along with my regular backup.
However, I do get sporatic log file full messages. I then have to run the
script through the query analyzer that appears to solve the problem untill
the next time.
regards
gilbert
"Greg D. Moore (Strider)" < mooregr_deleteth1s@g
reenms.com> wrote in message
news:J5VFe.10184$oZ.2845@newsread2.news.atl.earthlink.net...
>
> "Mike Epprecht (SQL MVP)" <mike@epprecht.net> wrote in message
> news:42e7ed30$1_1@ne
ws.bluewin.ch...
>
> Can I add though that this script is probably not a good idea.
>
> Either run the database in simple mode or perform actual log backups.
>
>
>
>
| |
| Greg D. Moore \(Strider\) 2005-07-28, 9:24 am |
|
"Myth of Sisyphus)." <teller_117@hotmail.com> wrote in message
news:5y4Ge.5644$q23.914966@news20.bellglobal.com...
> Hi Greg,
>
> I do have a log file backup scheduled along with my regular backup.
> However, I do get sporatic log file full messages. I then have to run the
> script through the query analyzer that appears to solve the problem
untill
> the next time.
But then you've completely invalidated your log backup chain.
I think you need to revisit your disaster recovery scenario since once
you've done the truncate, you can no longer recover anything past the last
transaction back up or full backup.
You're either better of doing transaction log backups more often to avoid
filling up your log, making your log larger, or finding out what's filling
them up.
>
> regards
>
> gilbert
>
>
> "Greg D. Moore (Strider)" < mooregr_deleteth1s@g
reenms.com> wrote in
message
> news:J5VFe.10184$oZ.2845@newsread2.news.atl.earthlink.net...
>
>
|
|
|
|