Videos / Other Resources

No attachments were found.

Database Update Utility

The Database Update Utility updates your Holdem Manager 2 database automatically.  This could take a significant amount of time on large databases!  
Please see below for common questions regarding the Database update.

Do I need to do the database update when I get the prompt?
Who should upgrade?
How long will it take?
Why does the updater take longer than a manual import?
I am worried I will lose my information.
Why do my results and stats differ?



Do i need to do the database update when i get the prompt?
No, you do not need to update right away.  You can choose no and run the updater at any future point.  It should prompt each time you load HM2.  However,
if it does not prompt just use Ctrl+Shift+U to manually launch the prompt to update.


Who should upgrade?
Anyone that installed v. 6866 or any of the internal versions before the official release of v7145.  If you have v7145 or higher you should not get the prompt
to update and you do not need to run it.


How long will it take?

We have made the following estimates on how long the updater should take based on your PC specs. This is just a rough estimate and it should be noted that
the updater will take longer to run than a manual import.

Low Spec – 50-70k hands per hour
Med Spec – 140-250k hands per hour
High – 300-400k hands per hour



Why does the updater take longer than a manual import?

The reason for this is because we also backup all your notes, hand markings, notecaddy notes, profiles, Tournament summaries and all relevant info.
Although a manual reimport would be faster it will require you to backup all the settings mentioned above so you can choose between the convenience of this one
click update or save some time and do a manual import if those settings are not important to you.

If you have any questions please post in the forums http://forums.holdemmanager.com/holdem-manager-2-0/ or email us via the 'Contact Support' link here.
 and well be happy to answer any questions you have.


I am worried i will lose my information?
Short Answer is you dont have anything to worry about as long as you dont delete your original database until after you've confirmed all the results and information 
transferred over as expected. We dont touch the original database so if anything goes wrong you just revert to the original database and try again.

So here is the procedure, in this example well assume your database is called holdemmanager:

Original Database Name: holdemmanager
After you click update holdemmanager, it creates a new database called holdemmanager_updated, we import all the updated information from the original database
into the holdemmanager_updated database leaving the original holdemmanager database untouched.

Once the database update is complete we first rename your original untouched database from holdemmanager to holdemmanager_obsolete since the
information in that is outdated (even though its your original) and you will be no longer using it.

We then name holdemmanager_updated which now contains the updated information to holdemmanager and this now becomes your primary database. Dont
delete this holdemmanager_obsolete database until your sure all your info was transferred over successfully.






dbupdate.png



PostgreSQL Cant Connect leading to empty database when using updater affecting a very small % of users:
If anyone has the issue where it says:

Cannot connect to PostgreSQL during the update youll find that it kills the updater, renames the new empty database to your original and renames your original to MyDatabase_obsolete which is not a good outcome.  It must be stressed regardless your original information is still completely intact as we never touch the original data only the database name.

In this version http://www.holdemmanager.com/Downloads/7232_Hm2AutoUpdate.exe there is an option to rename a database by first selecting the database and then choosing the edit button and rename it.  You cannot rename an active database so you need to make a different database active before you can rename the current one.  So you can rename your database if its incorrectly named and also delete the empty one.

That new version should also solve the issue from happening again, if anyone does get the message please send your log.txt file from C:\Users\YourName\AppData\Roaming\HoldemManager folder.  (XP users will find that in C:\Documents and Settings\YourName\AppData\Roaming\HoldemManager folder.)
If you have extensions turned off then it may be just called log.  Please email the log, directly after you have the issue and before you restart HM2, to paul.morny@gmail.com along with a link to the thread, if you restarted HM2 the log will not have the info.  
 




Why do my results and stats differ?

In some cases your results and stats will differ.  This is because we have fixed lots of parsing bugs and your results will be updated accordingly.  Any
manual edits you made to tournaments or summaries that were imported will all be carried across.  You will not lose that information.  See below for details of why
some of your stats may differ slightly.

We have made the following estimates on how long the updater should
take based on your PC specs. This is just a rough estimate and it should 
be noted that the updater will take longer to run than a manual import.
The reason for this is because we also backup all your notes, hand 
markings, notecaddy notes, profiles, Tournament summaries and all
relevant info.
Although a manual reimport would be faster it will require you to backup
all the settings mentioned above so you can choose between the 
convenience of this one click update or save some time and do a manual 
import if those settings are not important to you.

 


Stat Changes

What has changed?

Since HM2 build 6866, we improved how raise stats where we face a bet are calculated.  This applies to every raise stat, such as PFR, 3Bet, 4Bet, Resteal and others, 
including postflop stats. When downloading the newest version of Holdem Manager 2, you will be prompted to update your database to correct these stats. This
may take some time with larger databases. We suggest to do this when you have some downtime and do not expect to play for a few hours.


Example:
For example, the Button is a shortstack and you are in the Big Blind.  The Button Shortstack open shoves all in.

Previously, this counted as opportunity for 3bet (0/1 or 3bet 0 times from 1 possible opportunities).  But, in reality it was not an opportunity because you can not 3bet if the Button shortstack
is already all in.  So, it should be 0/0.

We changed the formula to correct this.  The result is this is no longer considered an opportunity to 3bet or (0/0 3bet%) instead of (0/1 3bet%).
For cash players the difference is minimal.  For tournament players where shortstacks and varying stack sizes are more frequent, the difference may be more noticeable.

Another change is your call/fold/raise % won’t always add up to 100%.  The logic previously was when facing a raise there was always 3 options, Fold, call or raise.  By that logic, since you always have three options and can only choose one of them, your % would always add up to 100%.  That logic is not always correct.  This is shown in the example above when accounting for the shortstack open shoving all in.

 

Lets run through an example:

Hand 1 you are on the button and shortstack raises and you call.

Result Call 100% (1/1), Fold 0% (0/1) and 3bet 0% (0/1) – 100+0+0 = 100%

Hand 2 you are on the button and shortstack raises and you fold.

Result Call 50% (1/2), Fold 50% (1/2) and 3bet 0% (0/2) - 50+50+0 = 100%


Hand 3 you are on the button and shortstack open shoves all in and you call.

Result with old system: Call 66% (2/3), Fold 33% (1/3), 3bet 0% (0/3) - 66+33+0 = 100%
Result with new system: Call 66% (2/3), Fold 33% (1/3), 3bet 0% (0/2) - 66+33+0 = 100%

 

Hand 4 you are on the button and the shortstack min raises and you 3bet him.

Result with old system: Call 50% (2/4), Fold 25% (1/4), 3bet 25% (1/4) - 50+25+25 = 100%
Result with new system: Call 50% (2/4), Fold 25% (1/4), 3bet 33% (1/3) – 50+25+33 = 108%


Notice Hand 1 and 2 do not differ under the new or old system.  But, notice in hand 3, the shortstack shoves all in.  Under the old system, that is not counted as an opportunity to 3bet because it is not possible if the shortstack is all-in.  Thus you can see that the old system shows 0/3 (3bet 0 times from 3 possible times) and the new system shows 0/2 (3bet 0 times from 2 possible times because it was not possible in hand 3).  On the 4th hand we can see where this causes the combined % to exceed 100%.

This logic was applied to all our stats (steal, 3bet, 4bet, 5bet).  So If player is already all in, you cannot raise and only call or fold and the opportunities will be adjusted.


Q: Why do some players have higher PFR than VPIP?

A: First of all, this only happens in games where you face a lot of all in situation (e.g. Shortstack games, tournaments). If you dont face all-ins, PFR will never be higher than VPIP.


Here is an example of how PFR changed:

Situation 1: (without all-ins)

You played 10 hands, called once and raised 2 times.

 

Previously:

That made your VPIP 30 (3 out of 10 times), PFR 20 (2 out of 10 times)

 

Now:

Exactly same as before, VPIP 30 (3 out of 10), PFR 20 (2 out of 10)

 

Situation2:

You play 10 hands, call once, raise 2 times (same as before), but you also face 4 all-ins)


Previously:

VPIP 30 (3 out of 10 times),

PFR 20 (2 out of 10 times)


Now:

VPIP 30 (3 out of 10 timeS)

PFR 33 (2 out of 6 times, you couldnt raise when facing 4 all-ins)

 

Q: Why is this good?

A: The new % is the more accurate representation of player's range in games with a lot of all-ins.  Think of it this way: are you more likely to raise all-in, or call an all-in?  For a lot of players, it holds true that they raise a much bigger % of their hands than what they call with and that's why you will see their PFR being higher than VPIP.

 

 

| More

Related Articles


User Opinions (29 votes)

96% thumbs up 3% thumbs down

How would you rate this answer?



Thank you for rating this answer.

Continue