Thanks for the information, I mention that I thought the view is stored similar to a normal table, because I read that here:

https://technet.microsoft.com/en-us/library/dd171921%28v=sql.100%29.aspx?f=255&MSPPError=-2147217396

This is the paragraph that I'm talking about:

• Additional storage is required in the database for the indexed view. The result set of an indexed view is physically persisted in the database in a manner similar to that of typical table storage.
• SQL Server maintains views automatically; therefore, any changes to a base table on which a view is defined may initiate one or more changes in the view indexes. Thus, additional maintenance overhead is incurred.

Thanks

Javier

Hi Sebastian,

Ok, I see what you are saying, and make sense. So, I'll investigate why I'm getting a performance improvement, maybe is just causing a different execution plan, or something like that, and I could create the same result without schemabinding, and that will solve my issue. 

Anyway, the view definition is still valid with schemabinding, I'm not getting any feedback from DNN, do you know, or anyone knows, who maintains EVS? I did not find the code on github, so, I guess is not the community.

Thanks

Javier