SQL2008 => SQL-Svr2017 [英] SQL2008 => SQL-Svr2017

查看:102
本文介绍了SQL2008 => SQL-Svr2017的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

升级到SQL Server 2017 ...




添加到查询:OPTION(USE提示('QUERY_OPTIMIZER_COMPATIBILITY_LEVEL_100')


我假设这告诉优化器使用SQL2008R2引擎而不是SQL2017来创建SQL计划。

解决方案

您好VikingExplorer,


兼容性级别仍适用于数据库的所有SQL Server部署选项(不适用于数据仓库)。


请参阅此博客:  Azure SQL数据库的默认兼容级别140(链接



  • sql-server-2019现在处于预览状态(兼容级别150)

博客建议插入您添加的T-SQL,以确保脚本在设计为运行reaso的环境中运行你已经证明了这一点。


附加信息:


ALTER DATABASE(Transact -SQL)兼容级别(链接





Upgraded to SQL Server 2017...

Added to Query: OPTION (USE HINT('QUERY_OPTIMIZER_COMPATIBILITY_LEVEL_100'))

I assume this tells the optimizer to use the SQL2008R2 engine instead of SQL2017 for SQL plan creation.

解决方案

Hi VikingExplorer,

Compatibility level still applies across all SQL Server deployment options for Databases (does not apply to Data Warehouse).

Please see this blog: Default compatibility level 140 for Azure SQL databases (Link)

  • sql-server-2019 is now in preview (compatibility level 150)

The blog recommends inserting the T-SQL you added to ensure the script runs in the environment it was designed to run in for reasons you have demonstrated.

Additional Information:

ALTER DATABASE (Transact-SQL) Compatibility Level (Link)


这篇关于SQL2008 => SQL-Svr2017的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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