SlimmGBPVR - replacement for GBPVRTray

[chud]

alright, i am thinking that SlimmGBPVR is not to blame for my database woes. i have had it turned off for a day and just checked my machine for the database size. pre EPG update it was something like 250MB. afterwards it is 309MB. i can almost hear Mick singing "i can't get no... data compaction..."

[Mister Slimm]

alright, i am thinking that SlimmGBPVR is not to blame for my database woes. i have had it turned off for a day and just checked my machine for the database size. pre EPG update it was something like 250MB. afterwards it is 309MB. i can almost hear Mick singing "i can't get no... data compaction..."

I've had the same thing aswell. The UpdateEPG doesn't seem to consistently compact. Luckily, mine only goes up for 3-4Mb a time. I have been doing some research as to how to release my connection to the database. The code I thought would do it doesn't and so SlimmGBPVR doesn't actually release it's connection at this time despite the Options and log saying to the contrary (it's trying, just not succeeding!).

I use a Connection, Command and Reader object. I set the Command and Reader to null, and close the Connection, then set it to null. This doesn't seem to release the Jet database lock. I have to quit SlimmGBPVR before the lock is released. If anyone knows how to definitively release a Jet database lock in .NET 2.0, I would welcome the help.

[Major Hostility]

I've been monitoring the auto-compaction behavior over the past few weeks since it isn't working very often for me, and believe I tracked down a "timing" problem that hopefully Sub can resolve in a future release.

What I've noticed is that the calls to "RequestDatabaseCompaction()" that are logged in GBPVRRecordingService.exe.log seem to occur before the EPG is fully updated, meaning that the recording service is still accessing the DB and therefore the compaction fails.

[Mister Slimm]

I've been monitoring the auto-compaction behavior over the past few weeks since it isn't working very often for me, and believe I tracked down a "timing" problem that hopefully Sub can resolve in a future release.

What I've noticed is that the calls to "RequestDatabaseCompaction()" that are logged in GBPVRRecordingService.exe.log seem to occur before the EPG is fully updated, meaning that the recording service is still accessing the DB and therefore the compaction fails.

Interesting. I've rewritten my utility to completely quit itself during the EPG update and reload in PostUpdateEPG.bat. Hopefully, the database compaction is also called before that batch file. I am due to test it during tomorrow morning's update (at 7am). Fingers crossed!

[Major Hostility]

Interesting. I've rewritten my utility to completely quit itself during the EPG update and reload in PostUpdateEPG.bat. Hopefully, the database compaction is also called before that batch file. I am due to test it during tomorrow morning's update (at 7am). Fingers crossed!

Unfortunately, my observation is that the call to compact the DB always occurs after the call to run PostUpdateEPG.bat as in:

Code:

3/23/2006 12:17:27 PM.000    INFO    [26]    Running PostUpdateEPG.bat
3/23/2006 12:17:27 PM.062    VERBOSE    [26]    RequestDatabaseCompaction()

[Mister Slimm]

Unfortunately, my observation is that the call to compact the DB always occurs after the call to run PostUpdateEPG.bat as in:

Code:

3/23/2006 12:17:27 PM.000    INFO    [26]    Running PostUpdateEPG.bat
3/23/2006 12:17:27 PM.062    VERBOSE    [26]    RequestDatabaseCompaction()

Bummer. Guess I'm gonna have to think of something else.

[UncleJohnsBand]

You are welcome to run this as a scheduled task at some other time like 45 minutes after your EPG update is scheduled. Do not put this in the postupdateepg.bat file.

(For Saftey.....make your own backup of the gbpvr.mdb file until you are comfortable with this and to see if any bugs crop up....)

It will stop the GBPVR Service, Create a backup of the GBPVR DB, compact the databse, then restart the GBPVR Service.

Note: If you are using the Web Admin hosted via IIS this will not work.....IIS seems to lock the DB.

[Mister Slimm]

BETA version: 1.1.2278.26726

As always, please note that this is a beta version. Comments appreciated.

Features:

• Time that the connection to the database is released can be set under Options->Advanced.
  
• Update EPG from menu now closes program down for Post Update EPG minutes (Options->Advanced) allowing update to compact database when finished.
  
• Program now automatically exits Pre Update EPG minutes (Options->Advanced) before UpdateEPG hour (set in GBPVR config) and restarts automatically Post Update EPG minutes after the UpdateEPG hour. This allows the update to compact the database.
  

Direct download link

[cginzel]

changing the post number does not update the restart time to the right, but changing the pre will...

[Mister Slimm]

changing the post number does not update the restart time to the right, but changing the pre will...

Thanks.

Beta version: 1.1.2281.21519

As always, please note that this is a beta version. Comments appreciated.

Features:

• Above bug fixed.
  

Direct download link