Warning: Constant WP_TEMP_DIR already defined in /var/www/html/blogs/joe/wp-config.php on line 93
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/joe/wp-config.php:93) in /var/www/html/blogs/joe/wp-includes/rest-api/class-wp-rest-server.php on line 1902
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/joe/wp-config.php:93) in /var/www/html/blogs/joe/wp-includes/rest-api/class-wp-rest-server.php on line 1902
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/joe/wp-config.php:93) in /var/www/html/blogs/joe/wp-includes/rest-api/class-wp-rest-server.php on line 1902
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/joe/wp-config.php:93) in /var/www/html/blogs/joe/wp-includes/rest-api/class-wp-rest-server.php on line 1902
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/joe/wp-config.php:93) in /var/www/html/blogs/joe/wp-includes/rest-api/class-wp-rest-server.php on line 1902
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/joe/wp-config.php:93) in /var/www/html/blogs/joe/wp-includes/rest-api/class-wp-rest-server.php on line 1902
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/joe/wp-config.php:93) in /var/www/html/blogs/joe/wp-includes/rest-api/class-wp-rest-server.php on line 1902
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/joe/wp-config.php:93) in /var/www/html/blogs/joe/wp-includes/rest-api/class-wp-rest-server.php on line 1902
{"id":1165,"date":"2014-03-02T13:53:18","date_gmt":"2014-03-02T21:53:18","guid":{"rendered":"http:\/\/3.209.169.194\/blogs\/joe\/?p=1165"},"modified":"2014-03-02T13:53:18","modified_gmt":"2014-03-02T21:53:18","slug":"using-the-sql-server-2014-database-compatibility-level-without-the-new-ce","status":"publish","type":"post","link":"https:\/\/www.sqlskills.com\/blogs\/joe\/using-the-sql-server-2014-database-compatibility-level-without-the-new-ce\/","title":{"rendered":"Using the SQL Server 2014 Database Compatibility Level without the New CE"},"content":{"rendered":"
Consider the following scenario:<\/p>\n
\n
You want to migrate all databases on a specific SQL Server instance to a new SQL Server 2014 instance<\/li>\n
You want to leverage new SQL Server 2014 functionality and move to the latest database compatibility level<\/li>\n
You don\u2019t<\/em> want to enable the new Cardinality Estimator right away (various reasons why this might be \u2013 but perhaps you didn\u2019t have time to fully test key workloads)<\/li>\n
You don\u2019t want to have to manually add QUERYTRACEON hints for specific queries<\/li>\n<\/ul>\n
To accommodate this scenario, you can do the following:<\/p>\n
\n
Change the migrated databases to COMPATIBILITY_LEVEL = 120 in order to leverage the SQL Server 2014 database compatibility level<\/li>\n
Enable trace flag 9481<\/u> at the server-level as a startup trace flag (or via DBCC TRACEON \u2013 but remembering this doesn\u2019t persist on restarts unless you re-execute)<\/li>\n<\/ul>\n
Trace flag 9481, for using the legacy CE behavior and trace flag 2312, for using the new CE behavior are both fully supported and documented by Microsoft here:<\/p>\n