Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6826565
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T22:09:45+00:00 2026-05-26T22:09:45+00:00

Is there a difference in performance between these two queries? –= operator SELECT COL1,

  • 0

Is there a difference in performance between these two queries?

--= operator
SELECT COL1, COL2 
FROM DBO.MYTABLE 
WHERE COL1 = '1'

--like operator
SELECT COL1, COL2 
FROM DBO.MYTABLE 
WHERE COL1 LIKE '1'

Basically using LIKE in this case is wrong but database engine accepts this.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T22:09:46+00:00Added an answer on May 26, 2026 at 10:09 pm

    Checkout the following post.

    Quote (in case it goes off-line):

    My knee-jerk response was that the = would be faster, but I thought
    about it and realized that the query optimizer would actually see them
    as the same thing. A check of the query plans against a
    quickly-created tbFoo confirmed it. So that’s what I told him.

    Except that I realized a moment later that there was a major caveat –
    the query optimization depends on how the statement is parameterized.
    If it’s purely ad hoc SQL and being compiled at run-time, then the
    statements are equivalent, but if there’s going to be any plan re-use,
    either by including the statement in a stored proc or preparing it and
    executing via sp_executesql, the LIKE will impose a significant
    penalty.

    This is because the optimizer doesn’t know at compile time whether the
    parameter to the LIKE operator will contain a wild card, so it can’t
    use the more specific optimization (including index selection) that it
    could with an = operator. So if you mostly pass parameters without
    wildcards, you will be executing a suboptimal query plan. Keep this in
    mind when designing your query!

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Is there any performance difference between the two following queries: SELECT foo,bar FROM table
When accessing values from an SqlDataReader is there a performance difference between these two:
Is there a performance difference between these two queries. Apparently WHERE should be reserved
Why is there such a huge performance difference between these two queries? -- (89
I am wondering if there is a performance difference between these two queries that
Is there a difference (performance, overhead) between these two ways of merging data sets?
Is there any performance difference between these two approaches? // First approach, iterating until
I just wanted to know that is there any performance difference between these two
Is there any difference between these two types of declarations performance-wise? local object =
Is there a performance and/or memory usage difference between these two scenarios? scenario 1:

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.