|
#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.
|
#4
|
|||
|
|||
Re: SQL: to convert or not to convert
[ QUOTE ]
[ QUOTE ] Well, PokerGrapher doesn't work, that's it. [/ QUOTE ] I converted to PostgreSQL AND got PokerGrapher to work. See this thread, 5 posts down. [/ QUOTE ] Sorry, but for those of us who don't know a thing about SQL and databases in general, I don't know where to look once I get past the control panel. |
#5
|
|||
|
|||
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).
|
#6
|
|||
|
|||
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. |
#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
[ QUOTE ]
Autohotkey script, self made, just record the import routine and loop. There might be of been an easier way to do it? [/ QUOTE ] so its not a pt function that combines the seberate db's? r u just exporting and re-importing the hands to the central db? |
#9
|
|||
|
|||
Re: SQL: to convert or not to convert
[ QUOTE ]
[ QUOTE ] Autohotkey script, self made, just record the import routine and loop. There might be of been an easier way to do it? [/ QUOTE ] so its not a pt function that combines the seberate db's? r u just exporting and re-importing the hands to the central db? [/ QUOTE ] Correct, and non-auto-import only accepts like 30 files at a time (had 1800 with overlap - both my exported HHs and backed up HHs). Could of tried adding an auto import directory, figured it might not of worked though. |
#10
|
|||
|
|||
Re: SQL: to convert or not to convert
[ QUOTE ]
Autohotkey script, self made, just record the import routine and loop. There might be of been an easier way to do it? [/ QUOTE ] any chance you could post how tod o this? I'm sick of having multiple databases |
|
|