Everything depends on situation. It is may be right when you talking about 5-10 lookup tables. It may create madness for the databases with 100-200...

As you can see in article, real life scenario 2 is more complicated than the one table. It consists of 4 tables (in my case). Based on 4 tables...

As you can see from real live example (scenario 2) code table have id as integer. Group and type tables are very small (50-100 records each). And in a lot of...

As you can see in article, real life scenario 2 is more complicated than the one table. It consists of 4 tables (in my case). I don't like codes...

I don't know the easier way to make transaction and process separation and at the same time keep them both real time.

As you can see in article, real life scenario 2 is more complicated than the one table. It consists of 4 tables (in my case). I don't like codes...

Based on my experience I do believe that clustered index should be for every table. If table don't have a good candidate for the clustered index for whatever reason then...