GBPVR.MDB is very large

[Landru]

Is it realistic to have a gbpvr.mdb grow to over 2gb? I don't seem to be having any problems withthe system, it's just that anything that accesses teh DB (like installing the latest version) takes forever and a day.....

Thanks!

Landru

[sub]

It tries to compact the database each night, by this will only work if you dont have any plugins or other utilities that maintain permanent connections to the database. The rate at which the database grows depends on how many channels you have, how many days of listing you have, and whether you've got the complete EPG reload option enabled.

Some plugins like the slimm tray thing are known to hold connections to the database, which will stop the system from being able to auto compact the database. I'm sure there are others too, but this is just an example that I knew of.

[Mister Slimm]

forum thread and beta download link

[Major Hostility]

It tries to compact the database each night, by this will only work if you dont have any plugins or other utilities that maintain permanent connections to the database. The rate at which the database grows depends on how many channels you have, how many days of listing you have, and whether you've got the complete EPG reload option enabled.

Some plugins like the slimm tray thing are known to hold connections to the database, which will stop the system from being able to auto compact the database. I'm sure there are others too, but this is just an example that I knew of.

For what it's worth, I'm beginning to suspect that having a copy of GBPVR.exe running in MVP server mode is also interfering with the automatic DB compaction after EPG update.

I'm going to try running with MVP auto-start set to 0 for a couple of days and see if it makes any difference.

[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.

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.

If anyone is interested......have been using this for several weeks now....I just setup a schedule to run this every day at a time I know I not recording anything and is after my EPG update....takes about 12-15 seconds to run.

Database stays between 10-12 meg.

GBPVR_Compact

[Jim_]

If anyone is interested......have been using this for several weeks now....I just setup a schedule to run this every day at a time I know I not recording anything and is after my EPG update....takes about 12-15 seconds to run.

Database stays between 10-12 meg.

GBPVR_Compact

Absolutely, thanks!
Would it be ok to use the utility in PostUpdateEPG.bat?

I’ve also noticed my mdb is becoming quite large, and config.exe doesn’t compact the database when it’s opened and closed using v0.96.12.
I stopped the recording service and used the “repair and compact” option in this utility and the 180-meg db shrunk to less than 6-megs.


Sub,
It sounds like it’s going to be quite some time before the next release, and this one’s working fine for me with the patches installed.
Is there any chance you could release a patch for this before moving to the next version?
Please?
Jim

[Mister Slimm]

After some headaches and false starts, Slimm GBPVR now definitely releases all locks on gbpvr.mdb.

forum thread and beta download link

[sub]

Sub,
It sounds like it’s going to be quite some time before the next release, and this one’s working fine for me with the patches installed.
Is there any chance you could release a patch for this before moving to the next version?
Please?

I'm not in a position to make patches to the current release. My version is now built against .net 2.0, so isnt compatible with the existing version.

That said, my database is compacting just fine on main v0.96.12 machine, so just try to make sure you're not using running any plugins or utilities that hold onto database connections and you should be ok.

I've made a few further enhancements in the next release to ensure the database stays small.

[Jim_]

That’s ok, the compact utility looks like a simple workaround.
Not sure when it started growing. I don’t have any plugins installed but I am using rectracker and it interfaces with the database at times.

No hurry with the next version, I’m actually quite happy with 96.12 at this point.

Jim

[UncleJohnsBand]

Absolutely, thanks!
Would it be ok to use the utility in PostUpdateEPG.bat?

I’ve also noticed my mdb is becoming quite large, and config.exe doesn’t compact the database when it’s opened and closed using v0.96.12.
I stopped the recording service and used the “repair and compact” option in this utility and the 180-meg db shrunk to less than 6-megs.

Jim

Jim...don't put it there....I tried that and it causes the GBPVR service to continually restart every 10 minutes or so for about an hour.....I think it has to do with the fact that the postupdateepg.bat is called from GBPVR and then when the compact utility stops the service GBPVR doesn't think it completed the EPG update correctly.

I simply went into control pannel, scheduled tasks and added a new one that runs the program about 45 minutes after the scheduled epg update. According to sub the EPG update can occur anywhere up to 1/2 hour past your scheduled time for the EPG update.