Database Model

Dec 8, 2015 at 4:12 PM
I just had a quick look at the solution. There's a lot to improve, in my opinion.
I would start from the DB Design.

Table [dbo].[Kunstwerks] contains too much data, i would say, all the data :)
Data should be divided, stored in different tables, and then aggregated into the [dbo].[Kunstwerks]

For ex.:
Instead of providing 4 fields with the description in 4 languages, create a table: [dbo].[Descriptions]
with columns [Id],[DescrNL],[DescrFR],[DescrDE],[DescrEN]; store the descriptions here, and then link the Description with the Kunstwerks by storing the Id of the Descption into the [dbo].[Kunstwerks]

And so on..

p.s.: can we use English names for tables and columns please?

Dec 9, 2015 at 3:23 PM
very good idea. You can change the columns in English names no problem,, I will do so in the future too.
And if you have time , you can change the code ,Make it better , Ofcourse I will do the same.