Path: csiph.com!news.swapon.de!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Anton Shepelev Newsgroups: comp.databases.ms-sqlserver Subject: Re: Make a backup only if necessary Date: Sun, 2 Jun 2024 14:43:20 +0300 Organization: A noiseless patient Spider Lines: 36 Message-ID: <20240602144320.325085f5f455d2f954cced20@gmail.moc> References: <20240527125929.d701039c2aec3196dc3d4731@g{oogle}mail.com> <20240528124112.80ab65ec4a358da57093539b@g{oogle}mail.com> <20240529005233.d0405d2f6f826fd0e8ae0624@gmail.moc> <20240531135309.a107b0e4fc99f9659bed7d8c@g{oogle}mail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Injection-Date: Sun, 02 Jun 2024 13:43:21 +0200 (CEST) Injection-Info: dont-email.me; posting-host="7493a2fdb12f13c092b5996420921596"; logging-data="3513119"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+Gw5c/W74RE2D5pm992Lq/kF38XKJCZi0=" Cancel-Lock: sha1:r+NAEUD9Olwo2k4smQ2wNBvfFf0= X-Newsreader: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Xref: csiph.com comp.databases.ms-sqlserver:2255 Erland Sommarskog: > Since you are settling on a recovery strategy that few > other people would consider, I'm afraid that you are quite > much on your own. 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. > Beside the fact that fn_dblog being undocumented, Yet it is a function of long standing: and statiscitally the longer something has existsed, the longer is its expected reamaining lifespan. Back in 2010 the function's author reassured users that rumours of its death were greately exagerrated: The Future -- fn_dblog() No More? > 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? -- () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments