GetTimetable/Synergetic: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
== FAQ == | ==FAQ== | ||
=== The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.ImportFromDB_SkemaBrikker === | ===The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.ImportFromDB_SkemaBrikker=== | ||
This could be the result of | This could be the result of someone scheduling the same class with '''PeriodNumberSeq = 1''' and '''PeriodNumberSeq <> 1''' | ||
It will give an error that ends with something like this '''04-02-19_08:40_09:43_PKMQ_2019_1''' | |||
This can help find the problematic timetable block. Decipher it like this | |||
# Date = 04-02-19 | |||
# Start time = 08:40 | |||
# End time = 09:43 | |||
# Classcode = PKMQ | |||
# FileYear = 2019 | |||
# ActualSemester = 1 | |||
The date is calculated based on 2 weeks schedule. This means the date is not too usefull. | |||
You can look in UMS using this SQL to find the date number | |||
<nowiki>Select *<br>From ImportFromDB_TimeTable_Synergetic<br>Where<br>Skemabegivenhed_ID = </nowiki> |
Revision as of 19:35, 14 January 2019
FAQ
The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.ImportFromDB_SkemaBrikker
This could be the result of someone scheduling the same class with PeriodNumberSeq = 1 and PeriodNumberSeq <> 1
It will give an error that ends with something like this 04-02-19_08:40_09:43_PKMQ_2019_1
This can help find the problematic timetable block. Decipher it like this
- Date = 04-02-19
- Start time = 08:40
- End time = 09:43
- Classcode = PKMQ
- FileYear = 2019
- ActualSemester = 1
The date is calculated based on 2 weeks schedule. This means the date is not too usefull.
You can look in UMS using this SQL to find the date number
Select *<br>From ImportFromDB_TimeTable_Synergetic<br>Where<br>Skemabegivenhed_ID =