#1
|
|||
|
|||
SQL: to convert or not to convert
I'm somewhat tech-savvy, but this SQL thing is beyond my level of understanding, and I'd be very appreciative if someone with more tech knowledge than me could post an informative post laying out the pros and cons of converting one's PT DB to SQL. From my limited knowledge, all I understand is that it would make everything -- from importing to viewing stats -- run much quicker. It would also remove the 2 gig max size of Access DBs.
But what (if any) are the downsides? - does it require a lot of tech knowledge to convert? - do HUDs (specifically PAHUD) work with SQL format PT DBs? - any other drawbacks? |
#2
|
|||
|
|||
Re: SQL: to convert or not to convert
Do it. It takes minutes to set up, it runs much faster than an access database, and PAHud works great. No downside that I see. Well, PokerGrapher doesn't work, that's it.
|
#3
|
|||
|
|||
Re: SQL: to convert or not to convert
Setup was pretty easy, took me around 24 hours to merge my 3 DBs (used a macro).
|
#4
|
|||
|
|||
Re: SQL: to convert or not to convert
[ QUOTE ]
Setup was pretty easy, took me around 24 hours to merge my 3 DBs (used a macro). [/ QUOTE ] Where did you get the macro? Or is this a self done jobby? Do tell, do tell. |
#5
|
|||
|
|||
Re: SQL: to convert or not to convert
[ QUOTE ]
Setup was pretty easy, took me around 24 hours to merge my 3 DBs (used a macro). [/ QUOTE ] is there any reason to have multiple DBs anymore? does it make a in storage space if u make 1. right now i have a db for limit,nl,and observed hands. |
#7
|
|||
|
|||
Re: SQL: to convert or not to convert
Autohotkey script, self made, just record the import routine and loop. There might be of been an easier way to do it?
|
#8
|
|||
|
|||
Re: SQL: to convert or not to convert
I don't see any reason to have multiple DBs anymore, other than having seperate autorate rules.
|
#9
|
|||
|
|||
Re: SQL: to convert or not to convert
[ QUOTE ]
I don't see any reason to have multiple DBs anymore, other than having seperate autorate rules. [/ QUOTE ] I still see performance problems with DBs that have hundreds of thousands of hands, even with PostgreSQL. |
#10
|
|||
|
|||
Re: SQL: to convert or not to convert
I still see performance problems in trying to open the ring games window for a large (200,000+ hands) DB.
The operation to backup the DB is MUCH faster with SQL though. JWP |
|
|