Products

Solutions

Learn More

Partners

Community

Blog

About

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsExtension Verif...Extension Verif...Problems creating view with schemabindingProblems creating view with schemabinding
Previous
 
Next
New Post
8/4/2016 7:26 AM
 
Javier,
according to http://www.sqlhammer.com/sql-server-s..., there is no table created upon schema-binding, it is more like a FK constraint to the DB schema, which might improve query plans, especially for user defined functions (see https://blogs.msdn.microsoft.com/sqlp...). On views, performance will significantly be improved if you add an index onto the view, which matches your query - in this case the view performs like a single query. Be aware that it only works for view on a single table or multiple tables with inner joins.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/5/2016 10:35 AM
 

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




Javier Rodríguez
CTO
www.AccordLMS.com
1775 W. State Street Suite 371, Boise ID 83702 USA
 
 
New Post
8/5/2016 12:22 PM
 
Javier,
- Additional space is required *for an indexed view* - i.e. for the index, not for the schema binding
- indexed views might require index maintaining overhead for adding / updating rows in base table - like an additional index on the table itself would do.
Schema binding is a pre-requisite for indexed views, but only the indexes provide the behavior like single tables.
Best,
Sebastian

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/8/2016 2:37 PM
 

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




Javier Rodríguez
CTO
www.AccordLMS.com
1775 W. State Street Suite 371, Boise ID 83702 USA
 
 
New Post
8/11/2016 10:17 AM
 
EVS is run by DNN Corp., AFAIR Nathan Rover was in charge of it, but I might be wrong.
Unfortunately, the Corp. is not always replying to requests.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsExtension Verif...Extension Verif...Problems creating view with schemabindingProblems creating view with schemabinding


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  

What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out