MS SQL Server 2008 中索引视图的性能影响
有人有在 MS SQL Server 2008 中使用索引视图的经验吗？ 我试图找出索引视图如何影响插入/更新语句的性能，这些语句在表中添加/更新行，这些行由索引视图使用（假设索引视图是将几个表连接在一起的选择）。鉴于视图底层选择结果的所有数据都被索引，我猜测幕后必须有一些“触发器”，在添加/更改某些内容时更新这些索引数据。但是我无法找到有关此事的任何有用信息。
Does anyone have experience with using indexed view in MS SQL Server 2008?
I am trying to find out how does indexed view affect performance of insert / update statements, that are adding / updating rows in tables, which are being used by the indexed view (assuming the indexed view is a select joining a few tables together). Given that all data that are result of the view's underlying select are indexed, I am guessing that there has to be some 'triggers' behind the scenes that update those indexed data when something is added / changed. However I wasn't able to find any useful information on this matter.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
此 msdn 链接是关于该主题的最后一句话：
http://msdn.microsoft.com/en-us/library/dd171921。 对于您的具体问题，请特别注意“设计注意事项”部分，特别
是“维护成本注意事项”子部分。
This msdn link is the last word on the subject:
http://msdn.microsoft.com/en-us/library/dd171921.aspx
For your specific question, pay special attention to the "Design Considerations" section, specifically the "Maintenance Cost Considerations" sub-section.
我认为将索引视图视为由系统触发器支持是足够有用的。性能影响应该是相似的。
I think it's useful enough to think of the indexed view as being supported by triggers by the system. The performance implications should be similar.