How to use MSDE(SQL Server) as GBPVR Database

[KingArgyle]

Only possible item I could see there is that filename is a reserved word in MSDE/SQL Server. I've had to reference it as [filename] in the past.

[cginzel]

It appears in this case, the problem was the length of the filename, not the column name "filename". The DTS import brought the column over as a nvarchar(255). I just increased it to nvarchar(512) and ran the EPG update again and the following error went away!

2/15/2005 8:16:58 AM.656 ERROR [139] Unabled to save ScheduledRecording: Specified cast is not valid.
2/15/2005 8:16:58 AM.656 ERROR [139] at bn.e(ScheduledRecording A_0)

Since I don't have any Access tools, can either of you tell me what the GBPVR database is using for a column length?

-Charles

[KingArgyle]

In .2313 it was a Text field of 255 characters. Not sure what it is in .9010. You can probably check the update.sql file that Sub usually includes in his distributions for any table changes that may have occured between releases.

[cginzel]

Well, I checked and the maximum data value length I have in the table is 98 characters long! I was thinking maybe sub was using a padded string that was being truncated with access and was complaining with MSDE... but I guess not. My working theory now is that sub is using a null terminated character array that must be defined as longer than 255 characters long but actually has shorter values in it.

Hey sub, One thing I did notice is that you are saving the full path including the file name in the database. In my "early" GBPVR days, I wanted to move the recorded files so I moved the files and updated the configuration but GBPVR did not recognize the change and now I understand why.

I would suggest that you not keep the path in the database, just keep the filename GBPVR generates. GBPVR should use the currently configure path and concatenate that to the filename from the DB. That way GBPVR will more gracefully and accurately handle moving of the recordings... Also GBPVR will be resistant to the use of some overly long configured path... since the user can select just about anything and GBPVR controls the filename generation.

Now having said that, I wonder if this would break some of those third party recording plug-ins...

-Charles

[KingArgyle]

Personally, I'd leave the filename with the full path as it is right now. Wait until after 1.0 is out the door, before looking at changing anything major like how filenames are handled and stored until after 1.0, too many plugins rely on this information.

[Ericwiz]

2/15/2005 8:16:58 AM.656 ERROR [139] Unabled to save ScheduledRecording: Specified cast is not valid.
2/15/2005 8:16:58 AM.656 ERROR [139] at bn.e(ScheduledRecording A_0)



Sounds like a NULL value issue.
Try this: Go into the tables and set all the fields to allow nulls. Then run this again and then go look at the data.

[cginzel]

Quote[/b] (Ericwiz @ Feb. 17 2005,12:14)]Sounds like a NULL value issue.
Try this: Go into the tables and set all the fields to allow nulls. Then run this again and then go look at the data.

No. I'm pretty sure the problem is the size of the filename column. Changing the width to 512 fixed this problem without changing null column settings...

-Cahrles

[DaveParker]

Hmm, anyone know a way to get Video Archiver to use SQL Server instead of its "video archive.mdb" file?

[KingArgyle]

Well, I would guess that it would be similiar on how to get GBPVR to use MSDE/SQL Server.

1. You'll need to import the Video Archiver database tables into a Database in MSDE.

2. Once that is done, you'll need to change the Provider that Video Archive is expecting to use. If it is using OLEDB (which I believe it is), then you be able to change it just like the GBPVR setting, but make it point to the Video Archiver database in the SQL Server.

As long as there aren't any Access specific SQL being used, you should be good to go.

[RonCS]

Hi,

It my first post here, so please be gentle! I've been playing with version 0.92.11 of GBPVR on a test box I have, trying to get a MSDE backend to function. I seem to be getting quite a few errors, that I believe I have tracked down to a possible typo in a delete function, this appears when I try and delete a source, it never succeeds and I am left with multiple sources, and a program table for of data. The line in question is:

delete from PROGRAMME p where channel_oid not in (select c.oid from CHANNEL c, SOURCE_CHANNEL_MAPPING scm where c.oid = scm.channel_oid)

I have looked though the forum, and seen that 'sub' answers with words of wisdom. Any advice??

Also has anyone got the definitive schema for MSDE?