PokerTracker

I have read that SSDs get destroyed over time if many small amounts of data get written on them often. That is exactly what the poker client (hand histories) and PT (writing the data from the hand histories into the database) do all the time, right?
Does PT/PostgreSQL therefore destroy my SSD?

I got a new pc with just an SSD (63 GB space free) and will get an HDD in a few months. Should I put everything poker-related on the SSD (because it is faster and I can use it immediately) or wait for the HDD (because poker is bad for the SSD)?

Thanks for your answers!

I've been using SSD hard drive for PT4 data storage for 4 years. Still works ok. Few months shouldn't be a problem. Besides, modern SSDs are much better protected from this kind of damage.

If you have the space, having your database on the SSD will improve PostgreSQL performance though for things like HUD usage it won't matter as much but will be better things like rebuilding your cache, and running complex custom reports. I've had an SSD for six years with PokerTracker 4, Holdem Manager 2 and PostgreSQL and it' s expected lifespan is for a few more years yet.

Thanks!
I will install everything on the SSD.

I already installed PT4 but the page https://www.pokertracker.com/user/mycodes.php only shows my PT3 registration code.
Where can I find my PT4 code and why is it not shown on that page?

Please let us know the following information in a Support Ticket (don't post the info in the forum):

1. The full name of the person who paid for PokerTracker especially if not you.

2. All possible email addresses in use at the time of doing so (it doesn't have to be the address you think was used so just send all those in use back then).

Alternatively if you have a running PokerTracker on another machine you can click "Help -> About" and let us know the name, email address and last six characters of the registration code that is displayed there.

Thanks for your help. I found out that I can link the order to my account myself. Now my PT4 code is shown and the problem is solved.

Great - thanks for the update.