A view is a predefined select-statement that can be used instead of a select on the table (or multiple tables). In TSQL, it is easier to use and gives the possibility to define different security settings. But the data of the view does not exist. It is calculated on the fly.
An indexed view is a view with an index on it so the data is materialized. The calculation of the data is maintained automatically by SQL server when updating the tables of the view.
In SSMS, other than the "tables"-item under the database, there is also a "views"-item.
Regards,Alain Krikilion No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
Indexed views are great :thumbsup:
The fact the Microsoft has removed the possibility to define which SIFT levels to maintain is awfull :thumbsdown:
During optimizations I often make new keys in NAV with MaintailSIFT=Yes but MaintainIndex=No.
That is the only way to make optimal indexed views for fast SIFT calculation.
It sux bigtime when your codebase is used in both SQL and Native installations. ](*,)
Comments
Many thank for your fastly reply but where is indexed viewer. Please guidance me
An indexed view is a view with an index on it so the data is materialized. The calculation of the data is maintained automatically by SQL server when updating the tables of the view.
In SSMS, other than the "tables"-item under the database, there is also a "views"-item.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
The fact the Microsoft has removed the possibility to define which SIFT levels to maintain is awfull :thumbsdown:
During optimizations I often make new keys in NAV with MaintailSIFT=Yes but MaintainIndex=No.
That is the only way to make optimal indexed views for fast SIFT calculation.
It sux bigtime when your codebase is used in both SQL and Native installations. ](*,)
Peter
As you can see, VSIFT can be tunned too.
I guess SIFT is replaced with VSIFT becouse it's slower in reading but .
Peter