Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.ms-sqlserver > #2256
| Path | csiph.com!news.swapon.de!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail |
|---|---|
| From | Erland Sommarskog <esquel@sommarskog.se> |
| Newsgroups | comp.databases.ms-sqlserver |
| Subject | Re: Make a backup only if necessary |
| Date | Tue, 04 Jun 2024 20:22:23 +0200 |
| Organization | Erland Sommarskog |
| Lines | 26 |
| Message-ID | <XnsB187CF3F51482Yazorman@127.0.0.1> (permalink) |
| References | <20240527125929.d701039c2aec3196dc3d4731@g{oogle}mail.com> <XnsB17FE71C2C3C7Yazorman@127.0.0.1> <20240528124112.80ab65ec4a358da57093539b@g{oogle}mail.com> <XnsB180CD77E5F89Yazorman@127.0.0.1> <20240529005233.d0405d2f6f826fd0e8ae0624@gmail.moc> <20240531135309.a107b0e4fc99f9659bed7d8c@g{oogle}mail.com> <XnsB18475BD5D7AYazorman@127.0.0.1> <20240602144320.325085f5f455d2f954cced20@gmail.moc> |
| MIME-Version | 1.0 |
| Content-Type | text/plain; charset=windows-1252 |
| Content-Transfer-Encoding | 8bit |
| Injection-Date | Tue, 04 Jun 2024 20:22:24 +0200 (CEST) |
| Injection-Info | dont-email.me; posting-host="3de9919d102e785172c079f34d5da139"; logging-data="576694"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/RZYisWl7okq2pWovts8me" |
| User-Agent | Xnews/2006.08.24 Mime-proxy/2.1.c.0 (Win32) |
| Cancel-Lock | sha1:54xVUAgI7k3uPKR7pbfbQ2wo+mo= |
| Xref | csiph.com comp.databases.ms-sqlserver:2256 |
Show key headers only | View raw
Anton Shepelev (anton.txt@gmail.moc) writes: >> you are also relying on that there are some rows left >> around in the log after a write operation. This is >> something that could change over time. > > Do you mean that in the future write operations may begin to > clear the log? > Since the log is truncated on checkpoint, the log could look empty. Then again, if you track LSN:s you should be safe. > 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. :-) Then again, following the normal routines saves quite a bit of human resources.
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