
12-10-2009, 11:59 AM
|
 | Senior Member | | Join Date: Mar 2009 Location: Russia, Moscow
Posts: 1,867
| |
Just some thoughts...
All the data stored in a 3rd-party database (PostgreSQL for PT3&HEM by default). So, it comes to how much data can the DB engine handle on your hardware without serious performance degradation.
This mainly depends on HDD speed/capacity, DB tables architecture and SQL queries optimization. The problem is for really huge amount of stored hands some database queries will start to work really really slow.
My guess is until you have tens of millions of hands in DB there shouldn't be serious problems. I'm almost sure this question was (is) discussed on PT3/HEM forums or covered in their FAQs/docs.
If you'll find some real numbers it would be interesting to see them here, just in case.
2nd, I haven't seen any way to manipulate already stored data in PT3/HEM programs, though I haven't searched for them. I'm pretty sure it is possible to do what you are asking about the hard way (manually via the DB admin tools and/or handwriting SQL queries). Alas, some programming skills will be necessary for that. Upd: you can just filter all the records that you wish to move out of DB and simply delete them (it's easy), and then create separate DBs for Absolute etc and re-upload hands into them from original HH-files.
Also, if you don't have original HH-files anymore, you can Export hands to HDD prior to deletion, and then load them into new DB. At least HEM allows this by right-clicking on selected hands. Ugh, hope I put it clear enough and haven't confused you
Last edited by podbelski; 12-10-2009 at 12:13 PM.
|