Company file on SSD?

[BookemDanno]

Our company file is quite large (yeah, I know that Intuit recommends that we collapse past years to discard historical detail, but we really don't wanna).

Operation is very slow due to read/writes (long waits listening to the disk grinding away).

QB Pro 2010
Single user (not shared--at least not at present).
Windows XP Pro on a two-year-old quad-core desktop.

I would like to put the company file (and whatever else is causing the read/write bottleneck) onto a SSD. I'm not looking to put anything else on that volume. I don't want to end up maxing out a 100- or 200-GB SSD by including all the program files for the dozens of other installed applications that aren't experiencing speed problems (but I will if that's the only way to make it work).

Nor am I really interested in reinstalling Windows onto the new disk (but, again, if that's the only way to do it, then maybe I'll have to look at larger SSDs). [Then again, if I have to do a new install of the OS, I might as well take the opportunity to upgrade to Windows 7, because, at some point, Intuit will likely drop XP support for future versions of Quickbooks, anyway.]

Is it possible to move just QB onto a separate drive, or does it have to be on the startup volume?

What else would have to go on there?--Would it be just the company file, the whole Documents\Intuit folder, or the entire All Users\Documents folder? How would I do it so that the system can find it? Would I need to change some Registry entries?

Would I also have to move the Program Files folder in order to experience any significant speed improvement from the SSD? Would I just reinstall QB and specify the new location? (It has been a long time since I installed, and I don't recall whether there is even an option to put it anywhere except the default directory.) Again, how can I get the system to find it?

Also. how could I get Windows and Quickbooks to use the SSD instead of the HDD for paging?

Sorry if these seem like real newbie questions. I find that I lack a lot of what seems to be pretty basic knowledge of how Windows works. When I monkey with the nuts and bolts of the OS, it's usually only because I'm following some online instructions to fix specific problems, not because I have a good grasp of what I'm doing.

Dan