This web site provides lessons and topics on how to use Microsoft SQL Server 2012 to create and manage databases.I am going to design a DW and I heard about materialized views. The tricky part is: the view has to satisfy quite a number of constraints and limitations - those are outlined in the white paper. The view is being updated automatically, no maintenance needed. So, many views that need better performance can't use this method. Although purely from engineering perspective, indexed views sound like something everybody could use to improve performance but the real life scenario is very different.

For example, the view can't reference other views and can't contain outer joins.

You work in a shop that puts business or application logic in the SQL Server using stored procedures, views and functions to return values to the calling applications or perform tasks.

This is not unusual in companies that use the SQL Server layer to perform business tasks, such as finance operations, or incorporate application functionality into the programmability layer.

I’m going to be outlining the practices that in my experience have given my clients the biggest benefits when working with their Very Large Databases. Use Multiple Filegroups A lot of times a VLDB will start in life like any other small database and keep growing and growing over time.

I will also explain why this particular item is important and make any notes about version or usage as necessary. The criticality of each one of these depends on your particular environment so I will leave that to you as a DBA to decide which ones should have a higher priority. Suddenly the DBA is left with multiple TBs and all on a single PRIMARY filegroup.