working to optimise db

i think in any version of nop db has own none optimization
for example in nop 1.9 a lot of forigns key is omited!!! for example costumerId in order table and etc.
in nop 2.0 the size of fields is not suitable and some type of data must be int but is nvarchar,a lot of nvarchar(max),
and dont use varchar data type when field is ascci
i think db is awful that for big project as nop with very good design is not good!!

any idea?

Hi,

I think you might be bringing a good point, but you need to elaborate on specific problems. I'm sure if you can come up with actual solutions to problems you think exist, the team will surely have a look at it.