On Mon, Feb 14, 2011 at 11:50 PM, Black, Michael (IS) < michael.bla...@ngc.com> wrote:
> And if you want to talk about data reliability...BACK UP YOUR DATA. > The likely failure points I can think of are: > #1 Power supply (redundant supplies available) > #2 Hard drive smoked (and your data is toast anyways -- RAID can help). > #3 Blue screen (or kernel lockup on Unix) > #4 CPU smoked. (usually leads to #3) > #5 RAM smoked. (usually leads to #3) > #6 Motherboard smoked (usually just dies or #3) > > The only way to increase your reliability is to replicate and/or backup. > All the whining about acid-tested drives is a waste of time. #3 through #6 > have no solution though they shouldn't cause the hard drive corruption > you're worried about. And since #1 and #2 have solutions what's the > problem? > > I see some problem especially for sqlite since in contrary to server-side databases, it's more consumer-oriented. Firefox, Apple Mail to name a few. And if we remember that it's very portable we see other possibilities. For example, there's already Portable Firefox that is usually used from usb sticks. What's going to happen to user history of such browser if the user forget to safely unmount the flash drive in the middle of the page reloading? What about music-management software that is portable enough to be used right from the external hard-drive? You don't usually use PostgreSQL or MySql for such applications. Max _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
