地理复制数据库上的查询存储 [英] Query store on Geo replicated database

查看:80
本文介绍了地理复制数据库上的查询存储的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

因此,我在主数据库上启用了地理复制,并且我将辅助数据库用于报告目的.我发现的问题是副本的查询存储和建议未打开,因此性能建议已打开 副本上关闭. 

So I have Geo replication turned on on my primary database and I use the secondary database for reporting purposes. The issue I am finding is that Query store and recommendations are not turned on for the replica and thus Performance recommendation are turned off on the replica. 

似乎这是对副本的限制?有人知道我能做什么吗?尝试并尝试解决此限制吗?

It seems this is a limitation on replicas? Has anyone have any idea of what I can do so try and work through this limitation?

谢谢

推荐答案

似乎这是对副本的限制?

It seems this is a limitation on replicas?

正确.当前的查询存储实现必须写入数据库,这在只读数据库中是有问题的.

Correct. The current query store implementation must write to the database, which is problematic in a read-only database.

请考虑该反馈建议,以便Microsoft可以优先考虑此功能:

Consider upvoting this feedback suggestion so that Microsoft can prioritize this feature: https://feedback.azure.com/forums/908035-sql-server/suggestions/32899126-enable-query-store-for-collection-on-a-read-only-r


这篇关于地理复制数据库上的查询存储的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆