After using the software for a few days now, here's my report:
(1) It does run much better than before... NOT GOOD yet, but better (which means the older version was REALLY bad). The new software will still completely take over my computer from time to time, but its "better" than before. Still not acceptable as far as I'm concerned.
(2) This software does not delete the database files it creates in windows\temp. Those keep building up, at the rate of 8 new files each time you boot. This is not good, and I consider this a major bug. Your software needs to delete these temp files it creates. The more files that are there, the slower disk access will be, not to mention wasted disk space.
(3) Speaking of temp files... one of them is 64Mb long, and the other is 10Mb long. No wonder the software is so slow, and banging away at my hard drive. What on earth are you storing in these files? The only thing you should ever have to store, is pathname and date/time of last modification, of the files/folders I've selected for backup. I can't imagine that data consuming this much disk space. I almost think you should be able to do that in memory. I would hope you're not using these files, to store "data" that is about to be copied, and I would hope you're not wasting time tracking path/dat/time information for files and folders I'm not even backing up.
(4) After all this, if you still need to use temp disk files, they should not be located in \windows\temp. They should be located in one of the \documents and settings\ temp file areas, so disk cleanup can delete them, should the computer be rebooted abnormally, before your software has a chance to delete the files it created.
(5) Is using SQL part of the problem? Is it just a CPU/resource hog? I just don't know.