|
|
#2
10-18-2006, 10:00 AM
|
|||
|
|||
Re: seperate datebases for different sites
If you think they're going to get really big (ie you play or datamine a ton), it would probably be smart to make 3 separate ones. Otherwise one would work and would be more convenient.
|
|
#4
10-19-2006, 01:48 AM
|
|||
|
|||
|
Re: seperate datebases for different sites
Let's talk a little more about this Casshern. I originally set up different databases for each site. Later I realized PAHud may be able to combine data from multiple databases in the calcs. True? If so, it won't double count the same hands if they're in two separate databases?
What do you think the ideal setup should be. One database for our hands, all sites, then another for observed hands (or multiple databases for heavy datamining?) How are you set up?
|
|
#5
10-19-2006, 02:48 AM
|
|||
|
|||
|
Re: seperate datebases for different sites
[ QUOTE ]
it won't double count the same hands if they're in two separate databases? [/ QUOTE ] If you have the same hand in two databases and PAH is using both it will get doubled...
|
|
#6
10-19-2006, 09:13 AM
|
|||
|
|||
|
Re: seperate datebases for different sites
Because if you use several databases for several sites, you will inevitably import hands in the wrong database at some point. If you have 10 databases for different sites and different limits you'll go crazy. It's also pretty much useless ... in PT you can specify you only want to see stats from limit x and site y ...
All my hands are in the same database. As for observed hands, I put them in a separate database. For 2 reasons. First, those hands won't slow down PT when I look at my own stats since they are in a separate Db. Also, because I want to be able to delete old observed hands after a while. After a year or so, the observed hands are pretty much useless ... I won't see the same players and if I do, they will play differently. If the observed hands are in 'your' database, you'll have a hard time to delete old observed hands ... So I create a new observed database every quarter. 2006-Q1 2006-Q2 2006-Q3 2006-Q4 When I create 2007-Q1, I will delete 2006-Q1
|
|
#7
10-19-2006, 09:58 AM
|
|||
|
|||
|
Re: seperate datebases for different sites
Good post C.
|
|
#8
10-19-2006, 10:57 AM
|
|||
|
|||
|
Re: seperate datebases for different sites
I have one database for "my hands".... then separate databases for "observed hands" at the different sites.... that works well for me, but I do have to be careful to not mix up the db's when i'm importing hand histories
|
|
#10
10-19-2006, 12:54 PM
|
|||
|
|||
|
Re: seperate datebases for different sites
I used to have everything in one db, but that db was getting big and slow when I wanted to analyze my ring stats for example. So the idea was to keep each db a more manageable size that wouldn't take too long to analyze stats with, etc. I have also purged the observed hand db's of the lower limits that I no longer play to keep them more manageable in size as well.
|
 |
|
|
Linear Mode
