如何以受支持的方式使用覆盖索引视图？
根据不支持的自定义：
由于引用完整性或升级问题，也不支持向数据库添加表、存储过程或视图。
我有一个流程可以返回最近到期的电话供工作人员拨打。这造成了一个问题，因为我们是一个呼叫中心，已经有几百万个呼叫，并且每天还会增加几千个。
我想添加一个索引视图，它提供覆盖索引少数人基表中所需的字段。这将按截止日期和我们使用的其他标准进行索引。我估计每次请求下一次调用时，这可以将约 1000000 次逻辑读取减少到少于 100 次。
我知道支持添加普通索引，但不支持添加视图。上面给出的原因是 RI 和升级。 RI 会成为问题吗？我不会更改数据的任何约束，只是跟踪其中的内容。 升级会成为问题吗？这只是一个索引，我可以在任何升级期间放弃它。
According to Unsupported Customizations:
Adding tables, stored procedures, or views to the database is also not supported because of referential integrity or upgrade issues.
I have a process that returns the most recently due phone call for staff to dial. This is causing a problem because we are a call centre, with a couple million calls already and adding a few thousand a day.
I'd like to add an indexed view which provides a covering index for the few fields required from the base tables. This will be indexed by due date and other criteria we use. I've estimated this could reduce ~1000000 logical reads every time the next call is requested to less than 100.
I know that adding a plain index is supported, but adding a view is not. The reason given above are RI and upgrades. Will RI be an issue? I'm not changing any constraint on the data, just keeping track of what is there. Will upgrades be an issue? It's only an index, I could drop it for the duration of any upgrades.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我们过去添加了自定义视图。升级（以及汇总）对于添加存储过程、视图等任何对象都会产生问题。为了避免出现问题，我们在修补过程中删除了它们。这显然不受支持，但众所周知，Microsoft 支持甚至支持不受支持的更改。
We have added custom views in the past. Upgrades (as well as rollups) will be a problem for adding any objects like stored procs, views, etc. We have dropped them during the patching to avoid issues. THis is obviously unsupported, but Microsoft support is known to support even unsupported changes.