Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.ms-sqlserver > #2257
| From | Anton Shepelev <anton.txt@g{oogle}mail.com> |
|---|---|
| Newsgroups | comp.databases.ms-sqlserver |
| Subject | Re: Make a backup only if necessary |
| Date | 2024-06-05 17:15 +0300 |
| Organization | A noiseless patient Spider |
| Message-ID | <20240605171517.0b0e856d919630ebaf31cfb7@g{oogle}mail.com> (permalink) |
| References | (4 earlier) <20240529005233.d0405d2f6f826fd0e8ae0624@gmail.moc> <20240531135309.a107b0e4fc99f9659bed7d8c@g{oogle}mail.com> <XnsB18475BD5D7AYazorman@127.0.0.1> <20240602144320.325085f5f455d2f954cced20@gmail.moc> <XnsB187CF3F51482Yazorman@127.0.0.1> |
Erland Sommarskog:
> Since the log is truncated on checkpoint, the log could
> look empty.
Indeed. I wish I knew how to track LSNs more reliably.
> Then again, if you track LSN:s you should be safe.
Do you mean your suggestion to use `RESTORE HEADERONLY'? If
so, I have already remarked that its FirstLSN LastLSN fields
are also available from the msdb.backupset table.
Unfortunately, tracking them produces a lot of false
positives, because of all the event types, I need only those
that refer to data changes, that is:
LOP_INSERT_ROWS, LOP_MODIFY_ROW, LOP_DELETE_ROWS
Other events should not trigger a backup.
> > I believe my situation is not unique, when there are
> > many infrequently used databases and no requirement of a
> > 15-minute backup granularity, so that keeping the simple
> > recovery model and doing a backup /only/ when data has
> > changed safes a log of resources.
>
> Log of resources, hehe. :-)
Of course, so that nothing slips by.
> Then again, following the normal routines saves quite a
> bit of human resources.
At the expense of increased boredom, and customisation.
--
() ascii ribbon campaign -- against html e-mail
/\ www.asciiribbon.org -- against proprietary attachments
Back to comp.databases.ms-sqlserver | Previous | Next — Previous in thread | Next in thread | Find similar
Make a backup only if necessary Anton Shepelev <anton.txt@g{oogle}mail.com> - 2024-05-27 12:59 +0300
Re: Make a backup only if necessary Anton Shepelev <anton.txt@g{oogle}mail.com> - 2024-05-27 13:53 +0300
Re: Make a backup only if necessary Erland Sommarskog <esquel@sommarskog.se> - 2024-05-27 22:43 +0200
Re: Make a backup only if necessary Anton Shepelev <anton.txt@g{oogle}mail.com> - 2024-05-28 12:41 +0300
Re: Make a backup only if necessary Erland Sommarskog <esquel@sommarskog.se> - 2024-05-28 20:11 +0200
Re: Make a backup only if necessary Anton Shepelev <anton.txt@gmail.moc> - 2024-05-29 00:52 +0300
Re: Make a backup only if necessary Anton Shepelev <anton.txt@g{oogle}mail.com> - 2024-05-31 13:53 +0300
Re: Make a backup only if necessary Erland Sommarskog <esquel@sommarskog.se> - 2024-06-01 11:34 +0200
Re: Make a backup only if necessary Anton Shepelev <anton.txt@gmail.moc> - 2024-06-02 14:43 +0300
Re: Make a backup only if necessary Erland Sommarskog <esquel@sommarskog.se> - 2024-06-04 20:22 +0200
Re: Make a backup only if necessary Anton Shepelev <anton.txt@g{oogle}mail.com> - 2024-06-05 17:15 +0300
Re: Make a backup only if necessary Anton Shepelev <anton.txt@g{oogle}mail.com> - 2024-06-05 19:37 +0300
csiph-web