This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Are there any performance penalties that we need to consider before creating views? If we create a view by joining several tables, does inserts/updates to the tables underlying the view take longer? Thanks for any help, Ramesh
I suppose there's some overhead to decide if your update is supported by the database. But this is probably not large and in any case should only be incurred once (at least if you use prepared statements). Beyond that, I would take a careful look at the execution plan for the update. Sometimes operations on views can expose optimizer quirks.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com