How to use MSDE(SQL Server) as GBPVR Database

[Urbansk]

Hi Spartan!

Some more info in this tread http://forums.nextpvr.com/showthread.php?t=16358

Do you have any trouble scheduling a whole season?
Can you provide the DDL for your database?

[Spartan]

Hi Spartan!

Some more info in this tread http://forums.nextpvr.com/showthread.php?t=16358

Do you have any trouble scheduling a whole season?
Can you provide the DDL for your database?

I've not had any problems whatsoever. I do have 2 recurring recordings set up and they work fine.

Attached are 2 files -- one to create the database and one to create the table schema.

[Urbansk]

In what forms are the scripts. After unzipping the files I can not open the files in notepad or QA.

[Spartan]

In what forms are the scripts. After unzipping the files I can not open the files in notepad or QA.

Works just fine for me. Use WinRAR to unzip.

[Urbansk]

I had to install a Download manger to get them properly downloaded.

[Urbansk]

I've not had any problems whatsoever. I do have 2 recurring recordings set up and they work fine.

Attached are 2 files -- one to create the database and one to create the table schema.

Using the DDLs provide i still get the same error when trying to schedule "record season (all episodes on this channel)"

[Spartan]

Using the DDLs provide i still get the same error when trying to schedule "record season (all episodes on this channel)"

So what is the exact error you are getting?

[Urbansk]

So what is the exact error you are getting?

2006-05-31 19:39:54.582 VERBOSE [1] RecordingFactory.save()
2006-05-31 19:39:54.598 ERROR [1] Unabled to save ScheduledRecording: Invalid character value for cast specification.
2006-05-31 19:39:54.598 ERROR [1] at System.Data.OleDb.OleDbCommand.ExecuteReaderIntern al(CommandBehavior behavior, String method)
at System.Data.OleDb.OleDbCommand.ExecuteNonQuery()
at GBPVR.Backend.Common.x396614b3dae3b1da.xc979432fcc 5a510a(ScheduledRecording xe41d2b9d98dc1269)
2006-05-31 19:39:54.598 VERBOSE [1] RecordingFactor.ScheduleSeasonRecordings(8, Lilla Röda Traktorn)

I think i have found some more info.

By using profiler have have fetched all querys to the database and then run them in Query analyzer. When i run this query i get the error:

Error converting data type varchar to datetime

The query:

exec sp_executesql N'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 (@P1,@P2,@P3,@P4,@P5,@P6,@P7,@P8,@P9,@P10,@P11,@P1 2)',N'@P1 int,@P2 int,@P3
nvarchar(19),@P4 int,@P5 int,@P6 int,@P7 int,@P8 datetime,@P9 datetime,@P10 int,@P11 int,@P12 int',177748,2,N'Lilla röda traktorn',4,40,5,16,''2006-06-21
17:00:00:000'',''2006-06-21 20:00:00:000'',1,1,2



If i remove all time entrys and leave the dates it works.

[Spartan]

Error converting data type varchar to datetime

The query:

exec sp_executesql N'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 (@P1,@P2,@P3,@P4,@P5,@P6,@P7,@P8,@P9,@P10,@P11,@P1 2)',N'@P1 int,@P2 int,@P3
nvarchar(19),@P4 int,@P5 int,@P6 int,@P7 int,@P8 datetime,@P9 datetime,@P10 int,@P11 int,@P12 int',177748,2,N'Lilla röda traktorn',4,40,5,16,''2006-06-21
17:00:00:000'',''2006-06-21 20:00:00:000'',1,1,2

If i remove all time entrys and leave the dates it works.

There are some strange newlines in that SQL string. Can you post one without newline characters in it? I want to run it against my database.

[Urbansk]

There are some strange newlines in that SQL string. Can you post one without newline characters in it? I want to run it against my database.

exec sp_executesql N'
insert into RECORDING_SCHEDULETMP
(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 (@P1,
@P2,
@P3,
@P4,
@P5,
@P6,
@P7,
@P8,
@P9,
@P10,
@P11,
@P12)',
N'@P1 int,
@P2 int,
@P3 nvarchar(19),
@P4 int,
@P5 int,
@P6 int,
@P7 int,
@P8 datetime,
@P9 datetime,
@P10 int,
@P11 int,
@P12 int',
177748,
2,
N'Lilla röda traktorn',
4,
40,
5,
16,
''2006-06-21 17:00:00:000'',
''2006-06-21 20:00:00:000'',
1,
1,
2


If possible you can use SQL Server Profiler on your installation when you are scheduling "Record season (all episodes on this channel)" and se if you get an error in gbpvr.exe.log. I have provided a trace from my installation for comparision. The trace is started just before i press "record" in the schedule recording window. The trace is stopped when i get back to the search guide window. To minimize the amount of events i have stopped the recording service during the trace.