How to use MSDE(SQL Server) as GBPVR Database

[Ericwiz]

That's what jumped out at me too.
the Data Source=base\gbpvr should just be your server so it should be (local) or base if that is it's name.

Use Initial Catalog to specify the db.

[cginzel]

I had tried (local) but that didn't work. I just tried base and that doesn't work either. In both of those cases, the error says that no server exists. I have MSDE installed as a specific instance of GBPVR (you can have multiple instances running as separate databases on different ports at one time).

When I use base\gbpvr at least it seems to recognize the server it just fails the login...

-Charles

[Ericwiz]

When you login using QA what database are you in? If not gbpvr what happens if you change to gbpvr?

It could be that the gbpvr login has access to the msde but not the gbpvr db.

MSDE has standard SQL access turned off by default. I dont know why but *shrug*. Anyway, somewhere in the setup you can turn it on. I dont remember where but if you are comfortable accessing the registry just go here:
HKeyLocalMachine\Software\Microsoft\Microsoft SQL Server\ Instance Name\MSSQLServer\LoginMode
and change it from "1" to "2" for mixed mode.

Then if your login still doesn't work try using login=sa and pwd empty (assuming you did not give sa a password) and let us know how that works.

-Eric...

[cginzel]

Okay, so I uninstalled MSDE and then manually cleaned up the registry because the MSDE install was "remembering" my instancename when I was not specifying one! After doing that, I was able to get MSDE running with GBPVR using the (local) reference for the data source!

However, I'm getting the same problem I did way back when where the EPG update was complaining about an "Incorrect syntax near 'p'. " and "Specified cast is not valid." (I'm using the Zap2It as the source) I think I had that fixed at some point using the DTS import, but that is what I did this last time… so I'm not sure what's up here.

If anyone has a suggestion for this problem, please fire away… I will do more investigating tonight.

Thanks,
-Charles

[KingArgyle]

Cginzel, I haven't tried it with 9.0.10 yet, but youmight also want to try and import an XMLTV formatted version of Zap2It. Check with Sub and see if he is doing anything that is Access specific with the SQL in 9.0.10 that is different from the 23.13 import.

[sub]

Quote[/b] ]Check with Sub and see if he is doing anything that is Access specific with the SQL in 9.0.10 that is different from the 23.13 import.

No I dont think I'm doing anything that'll stop MSDE working, but I dont test with it so I dont know for sure. The v0.90 release removed the access specific uses of now()

[cginzel]

My bad! It seems for some reason the identities did not come over with the DTS Data import... and they did not all take the first time I tried to manually set them (it was a late night though!. Now that I have the identities set, the EPG update is a little better, but I'm still seeing the following error in the log:

2/14/2005 8:16:32 PM.187 VERBOSE [139] RecordingFactor.ScheduleSeasonRecordings(77, Nature)
2/14/2005 8:16:32 PM.203 VERBOSE [139] Found potential match at 2/20/2005 8:00:00 PM
2/14/2005 8:16:32 PM.203 VERBOSE [139] - scheduling this episode
2/14/2005 8:16:32 PM.203 VERBOSE [139] Looking for capture source to record: Nature
2/14/2005 8:16:32 PM.203 VERBOSE [139] Checking Cox Cable (DIRECT:Hauppauge PVR150:1)
2/14/2005 8:16:32 PM.218 VERBOSE [139] RecordingFactory.loadScheduleRecording()
2/14/2005 8:16:32 PM.234 VERBOSE [139] RecordingFactor.save()
2/14/2005 8:16:32 PM.250 ERROR [139] Unabled to save ScheduledRecording: Specified cast is not valid.
2/14/2005 8:16:32 PM.250 ERROR [139] at bn.e(ScheduledRecording A_0)
2/14/2005 8:16:32 PM.250 VERBOSE [139] Requesting recording service schedule reload
2/14/2005 8:16:32 PM.281 VERBOSE [139] Found potential match at 2/21/2005 2:00:00 AM
2/14/2005 8:16:32 PM.281 VERBOSE [139] - scheduling this episode
2/14/2005 8:16:32 PM.281 VERBOSE [139] Looking for capture source to record: Nature
2/14/2005 8:16:32 PM.281 VERBOSE [139] Checking Cox Cable (DIRECT:Hauppauge PVR150:1)
2/14/2005 8:16:32 PM.281 VERBOSE [139] RecordingFactor.save()
2/14/2005 8:16:32 PM.281 ERROR [139] Unabled to save ScheduledRecording: Specified cast is not valid.
2/14/2005 8:16:32 PM.281 ERROR [139] at bn.e(ScheduledRecording A_0)

Does any of that ring a bell with you sub? Do you know what specific SQL the EPG update is trying to run at that point? Maybe if you send it to me (SQl statement) I can run it locally and see what's up...

-Charles

[KingArgyle]

It looks like it it is trying to schedule a recording when it encounters the problem. Does the recording ever get scheduled???

Cginzel, if you continue to get this problem, a work around is to use the CDK Scheduler. It has been tested to work with MSDE as well as Access.

[cginzel]

Quote[/b] (KingArgyle @ Feb. 14 2005,21:36)]if you continue to get this problem, a work around is to use the CDK Scheduler. It has been tested to work with MSDE as well as Access.

First I'd like to see if sub will have enough patience to deal with me on this...

There may be a few issues left, but I think GBPVR is very close to working with MSDE straight up. I see the other threads about boosting performance in different ways, but honestly, I think using MSDE is one of the best ways... All data access is much faster as you know.

I'm tempted to try your CDK Scheduler simply for the priority scheduling, but I'd rather convince my wife that we need a second capture card!

-Charles

[sub]

The two bits of sql executed in that function are:

select max(recording_group) from RECORDING_SCHEDULE
insert into RECORDING_SCHEDULE (programme_oid, capture_source_oid, filename, status, recording_group, recording_type, manual_channel_oid, manual_start_time, manual_end_time, quality_level, pre_pad_minutes, post_pad_minutes) values (?,?,?,?,?,?,?,?,?,?,?,?)