SharePoint uses a single table (i.e.
dbo.AllUserData) with columns like
nvarchar1, nvarchar2, ..., nvarchar64 or
int1, int2, ..., int16 (193 columns altogether) to store all items from all lists in all site collections.
Can creating new indexes, recomputing statistics, etc. help?
Let's forget for now that it very likely to lose Microsoft support for SharePoint installation modified like this.
Am I right in thinking that such a design makes all classic databases tuning techniques useless?
Has anyone ever tried to solve performance problems of SharePoint in any other way than adding more/faster hardware?