Converting to PT3

[mickle]

My situation is that I have about 20 separate PT2 access databases. Some are on my pc, the more recent ones are on my laptop. I'd like to take advantage of PT3's ability to cope with one large database and to copy all my history into a PT3 database. Ideally, thereafter I'd like to be able to use either the laptop or pc and keep the 1 database up to date. I've gone through lots and lots of posts but am still a little confused.

To start with, is it best to convert the access databases into PostgreSQL databases, or should I simply import the hand histories? Should these hand histories be generated from the existing databases or old hand history, or does it make no difference? What happens if I have overlapping hand history between the 2 machines? ie Will PT3 ignore duplicates? I have hand history for sites which aren't supported in PT3. What will happen to those hands with these options?

Some of the databses include observed hands. Is there any way to get rid of hands which don't involve me?

After that, to keep things simple I am tempted to have 2 separate PT3 databases - one on each machine. The intention will be for them to be identical. I'll keep hand history in a shared directory and manually import hand history into the pc database if I decide to use my pc to play poker. Following this method, am I at risk of importing duplicate files or does PT3 take care of this?

To put the above into context, I'm not great with pcs and will be using PostgreSQL for the first time when I set up PT3.

[Peligroso]

To start with, is it best to convert the access databases into PostgreSQL databases, or should I simply import the hand histories? Should these hand histories be generated from the existing databases or old hand history, or does it make no difference? What happens if I have overlapping hand history between the 2 machines? ie Will PT3 ignore duplicates? I have hand history for sites which aren't supported in PT3. What will happen to those hands with these options?

The best way if you want to turn many databases into one big database is to export the hand histories and then import them into PT3 using manual import. It shouldn't make a difference whether you export hands out of your PT2 databases and then import those files, or if you import the hand history files directly into PT3. Duplicate hands will be recognized and not imported by PT3. Hand histories from sites not supported by PT3 will not get imported.

Some of the databses include observed hands. Is there any way to get rid of hands which don't involve me?

Right now, there's no way to purge specific hands from the database, but selective purge is one of our top planned features and should be added shortly.

After that, to keep things simple I am tempted to have 2 separate PT3 databases - one on each machine. The intention will be for them to be identical. I'll keep hand history in a shared directory and manually import hand history into the pc database if I decide to use my pc to play poker. Following this method, am I at risk of importing duplicate files or does PT3 take care of this?

PT3 will take care of duplicate hands. An easier method for you would however probably be if you simply shared the databases between the 2 computers though if you're having a network at home. See the following guide: How To: Network PostgreSQL Database.

[WhiteRider]

To start with, is it best to convert the access databases into PostgreSQL databases, or should I simply import the hand histories?

Use the Hand Histories.

Should these hand histories be generated from the existing databases or old hand history, or does it make no difference?

If you have the original files, use those. Otherwise, "Export Hand History Files" from PT2 and use those.

What happens if I have overlapping hand history between the 2 machines? ie Will PT3 ignore duplicates?

Duplicates will be ignored.

I have hand history for sites which aren't supported in PT3. What will happen to those hands with these options?

These hands will be ignored too - you will be able to import them again later when those sites have been added.

Some of the databses include observed hands. Is there any way to get rid of hands which don't involve me?

Not yet, selective purge will be added later.
Auto import can split observed and played hands into separate DBs, but I don't think that manual import uses that setting.

After that, to keep things simple I am tempted to have 2 separate PT3 databases - one on each machine. The intention will be for them to be identical. I'll keep hand history in a shared directory and manually import hand history into the pc database if I decide to use my pc to play poker. Following this method, am I at risk of importing duplicate files or does PT3 take care of this?

PT3 will handle duplicates - you don't need to worry about it.

To put the above into context, I'm not great with pcs and will be using PostgreSQL for the first time when I set up PT3.

If you install PT3 with postgres you shouldn't need to worry about postgres at all.
HOWEVER - if you're using Vista, read this:
Attn: Vista Users Installing PostgreSQL 8.3

[mickle]

Thanks for the replies.

I know that patches are released over time to allow for changes in hand formats. If I import old files, will PT recognise all of the various formats used by Poker Stars and Party Poker?

[tarix]

If I import old files, will PT recognise all of the various formats used by Poker Stars and Party Poker?

In my experience the answer is yes. However I think a bug crept into Beta 13 when importing certain Party Poker files that contain split pots. You might want to do all of your importing under Build 2 before trying out Beta 13.

[mickle]

I've got quite a few hands in an error folder going back in time. This error folder was created by PT after importing hand history previously. Is it worth putting these in the overall hand history folder I'm setting up or will they still be unrecognised?

[WhiteRider]

Try all the hands you have, and attach any that give errors to our Support system (zip them up first) so that the problem can be investigated.

[mickle]

I've had another look and the hands in question are from the cryptologic network ie unsupported at present, so query is resolved. Must say the conversion process was reasonably easy. Thanks for the clarification which I was asking for before I went for it. :D