Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.ms-sqlserver    |    Notorious Rube Goldberg contraption    |    19,505 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 19,488 of 19,505    |
|    Erland Sommarskog to Anton Shepelev    |
|    Re: Make a backup only if necessary    |
|    04 Jun 24 20:22:23    |
      From: esquel@sommarskog.se              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.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca