Two Plus Two Older Archives  

Go Back   Two Plus Two Older Archives > Internet Gambling > Software
FAQ Community Calendar Today's Posts Search

Reply
 
Thread Tools Display Modes
  #1  
Old 08-23-2005, 09:07 PM
teddyFBI teddyFBI is offline
Member
 
Join Date: Jun 2004
Posts: 99
Default 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?
Reply With Quote
  #2  
Old 08-23-2005, 09:18 PM
Dudd Dudd is offline
Senior Member
 
Join Date: Sep 2004
Posts: 203
Default 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.
Reply With Quote
  #3  
Old 08-24-2005, 09:34 AM
beaster beaster is offline
Member
 
Join Date: Jun 2005
Posts: 57
Default Re: SQL: to convert or not to convert

[ 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.
Reply With Quote
  #4  
Old 08-24-2005, 10:28 PM
Dudd Dudd is offline
Senior Member
 
Join Date: Sep 2004
Posts: 203
Default 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.
Reply With Quote
  #5  
Old 08-24-2005, 01:00 AM
illunious illunious is offline
Senior Member
 
Join Date: Oct 2003
Location: Wausau, WI
Posts: 247
Default 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).
Reply With Quote
  #6  
Old 08-24-2005, 01:38 AM
slavic slavic is offline
Senior Member
 
Join Date: May 2003
Location: \"Let me make it nearly unanimous -- misplayed on every street.\"
Posts: 1,675
Default 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.
Reply With Quote
  #7  
Old 08-24-2005, 01:59 PM
illunious illunious is offline
Senior Member
 
Join Date: Oct 2003
Location: Wausau, WI
Posts: 247
Default 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?
Reply With Quote
  #8  
Old 08-24-2005, 06:57 PM
TheIrishThug TheIrishThug is offline
Senior Member
 
Join Date: Jan 2005
Location: playing nl omaha h/l stud
Posts: 204
Default 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?
Reply With Quote
  #9  
Old 08-24-2005, 07:57 PM
illunious illunious is offline
Senior Member
 
Join Date: Oct 2003
Location: Wausau, WI
Posts: 247
Default 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.
Reply With Quote
  #10  
Old 08-25-2005, 12:39 AM
sthief09 sthief09 is offline
Senior Member
 
Join Date: Feb 2004
Location: duffman is thrusting in the direction of the problem (mets are 9-13, currently on a 1 game winning streak)
Posts: 1,245
Default 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
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 03:06 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.