Bobcares

SQL Server use legacy cardinality estimation on specific query

by | May 9, 2022

SQL Server use legacy cardinality estimation on specific query can be mastered easily with this guide. Read more. 

At Bobcares, we offer solutions for every query, big and small, as a part of our SQL Server Support.

Let’s take a look at how our SQL Server Support Team is ready to help customers push use legacy cardinality estimation on a specific query.

How to let SQL Server use legacy cardinality estimation on specific query

The Legacy Cardinality Estimator in the SQL Server is a result of histograms from indexes or statistics. In other words. SQL Server relies on constraint information as well as logical rewrites of queries to nail down cardinality.

The Cardinality Estimator is responsible for predicting the number of rows a query will return. Furthermore, it also determines the memory allocation of the query.

By default, the Legacy Cardinality Estimation is OFF. We have to set it to ON in order to use it in an older version of SQL Server.

Alternatively, we can also do this by changing the property on T-SQL as seen below:

ALTER DATABASE
    SCOPED CONFIGURATION
        SET LEGACY_CARDINALITY_ESTIMATION = OFF|ON;

However, enabling Legacy Cardinality Estimation affects all queries. In some cases, it may also damage the query performance. Fortunately, our SQL Server experts recommend using FORCE_LEGACY_CARDINALITY_ESTIMATION to prevent this from occurring.

Adding FORCE_LEGACY_CARDINALITY_ESTIMATION to the query forces the query optimizer to use an older version of Cardinality Estimation.

If we have a SQL Server database with a compatibility level set to 120 or above, we can activate the legacy cardinality estimator at the database level as seen below:

SQL Server use legacy cardinality estimation on specific query
ALTER DATABASE SCOPED CONFIGURATION
SET LEGACY_CARDINALITY_ESTIMATION = ON;
GO
SELECT name, value
FROM sys.database_scoped_configurations
WHERE name = 'LEGACY_CARDINALITY_ESTIMATION';
GO

As a result, we learned how to use legacy cardinality estimation.

[Need assistance with another query? We are available 24/7.]

Conclusion

In a nutshell, our skilled SQL Server Support Engineers at Bobcares demonstrated how to use legacy cardinality estimation on a specific query.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF