Mixing
LIKE [0-9] much slower than LIKE %
I have a somewhat complex view that selects a bunch of items and the amount of stock they have remaining. I want to narrow down the result set to items codes that conform to a pattern so that unwanted items are filtered out.
The item codes that I want to include are formatted as a 4 digit number, followed by a hyphen followed by another 4 digit number
1234-0001
I also want to include item numbers that are formatted as an 13-digit number (an ISBN which starts with 978), followed by a hyphen, followed by another 2 digit number.
9781234567890-01
Originally I planned to use the below, which would match all item codes that included a hyphen in.
SELECT *
FROM Vw_Stock
WHERE ItemCode LIKE '%-%'
Unfortunately not all of our item codes are that uniform and people have sporadically used hyphens in items that do not conform to the two accepted formats above, so I switched to the following.
SELECT *
FROM Vw_Stock
WHERE ItemCode LIKE '[0-9][0-9][0-9][0-9]-[0-9][0-9][0-9][0-9]'
OR ItemCode LIKE '[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]-[0-9][0-9]'
The query originally took 1 second and now it takes roughly 3 minutes 50 seconds. Why does it take so much longer? And is there a more efficient way for me to query against the item formats identified?
sql
sql-server asked Nov 20 '18 at 16:35
ryansinryansin
724825
|
show 3 more comments
I have a somewhat complex view that selects a bunch of items and the amount of stock they have remaining. I want to narrow down the result set to items codes that conform to a pattern so that unwanted items are filtered out.
The item codes that I want to include are formatted as a 4 digit number, followed by a hyphen followed by another 4 digit number
1234-0001
I also want to include item numbers that are formatted as an 13-digit number (an ISBN which starts with 978), followed by a hyphen, followed by another 2 digit number.
9781234567890-01
Originally I planned to use the below, which would match all item codes that included a hyphen in.
SELECT *
FROM Vw_Stock
WHERE ItemCode LIKE '%-%'
Unfortunately not all of our item codes are that uniform and people have sporadically used hyphens in items that do not conform to the two accepted formats above, so I switched to the following.
SELECT *
FROM Vw_Stock
WHERE ItemCode LIKE '[0-9][0-9][0-9][0-9]-[0-9][0-9][0-9][0-9]'
OR ItemCode LIKE '[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]-[0-9][0-9]'
The query originally took 1 second and now it takes roughly 3 minutes 50 seconds. Why does it take so much longer? And is there a more efficient way for me to query against the item formats identified?
sql
sql-server asked Nov 20 '18 at 16:35
ryansinryansin
724825
3
It's theOR, I believe.
– GSerg
Nov 20 '18 at 16:38
3
look at the Query execution plan
– Cato
Nov 20 '18 at 16:41
regex can be pretty costly. Out of curiosity, how well does it perform if you have a where clause like this:isnumeric(replace(ItemCode, '-', '')) = 1? Additionally, will your ItemCode have a lot of non-numeric values?
– RToyo
Nov 20 '18 at 16:41
1
Does itemCode have an index ?
– Patrick Honorez
Nov 20 '18 at 16:44
It may or may not help if you doWHERE ItemCode LIKE '[0-9][0-9][0-9][0-9]%' AND (ItemCode LIKE '[0-9][0-9][0-9][0-9]-[0-9][0-9][0-9][0-9]' OR ItemCode LIKE '[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]-[0-9][0-9]'). May be worth a try.
– GSerg
Nov 20 '18 at 16:44
|
show 3 more comments
I have a somewhat complex view that selects a bunch of items and the amount of stock they have remaining. I want to narrow down the result set to items codes that conform to a pattern so that unwanted items are filtered out.
The item codes that I want to include are formatted as a 4 digit number, followed by a hyphen followed by another 4 digit number
1234-0001
I also want to include item numbers that are formatted as an 13-digit number (an ISBN which starts with 978), followed by a hyphen, followed by another 2 digit number.
9781234567890-01
Originally I planned to use the below, which would match all item codes that included a hyphen in.
SELECT *
FROM Vw_Stock
WHERE ItemCode LIKE '%-%'
Unfortunately not all of our item codes are that uniform and people have sporadically used hyphens in items that do not conform to the two accepted formats above, so I switched to the following.
SELECT *
FROM Vw_Stock
WHERE ItemCode LIKE '[0-9][0-9][0-9][0-9]-[0-9][0-9][0-9][0-9]'
OR ItemCode LIKE '[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]-[0-9][0-9]'
The query originally took 1 second and now it takes roughly 3 minutes 50 seconds. Why does it take so much longer? And is there a more efficient way for me to query against the item formats identified?
sql
sql-server asked Nov 20 '18 at 16:35
ryansinryansin
724825
I have a somewhat complex view that selects a bunch of items and the amount of stock they have remaining. I want to narrow down the result set to items codes that conform to a pattern so that unwanted items are filtered out.
The item codes that I want to include are formatted as a 4 digit number, followed by a hyphen followed by another 4 digit number
1234-0001
I also want to include item numbers that are formatted as an 13-digit number (an ISBN which starts with 978), followed by a hyphen, followed by another 2 digit number.
9781234567890-01
Originally I planned to use the below, which would match all item codes that included a hyphen in.
SELECT *
FROM Vw_Stock
WHERE ItemCode LIKE '%-%'
Unfortunately not all of our item codes are that uniform and people have sporadically used hyphens in items that do not conform to the two accepted formats above, so I switched to the following.
SELECT *
FROM Vw_Stock
WHERE ItemCode LIKE '[0-9][0-9][0-9][0-9]-[0-9][0-9][0-9][0-9]'
OR ItemCode LIKE '[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]-[0-9][0-9]'
The query originally took 1 second and now it takes roughly 3 minutes 50 seconds. Why does it take so much longer? And is there a more efficient way for me to query against the item formats identified?
sql
sql-server sql
sql-server asked Nov 20 '18 at 16:35
ryansinryansin
724825
asked Nov 20 '18 at 16:35
ryansinryansin
724825
asked Nov 20 '18 at 16:35
ryansinryansin
724825
asked Nov 20 '18 at 16:35
ryansinryansin
724825
asked Nov 20 '18 at 16:35
ryansinryansin
724825
724825
3
It's theOR, I believe.
– GSerg
Nov 20 '18 at 16:38
3
look at the Query execution plan
– Cato
Nov 20 '18 at 16:41
regex can be pretty costly. Out of curiosity, how well does it perform if you have a where clause like this:isnumeric(replace(ItemCode, '-', '')) = 1? Additionally, will your ItemCode have a lot of non-numeric values?
– RToyo
Nov 20 '18 at 16:41
1
Does itemCode have an index ?
– Patrick Honorez
Nov 20 '18 at 16:44
It may or may not help if you doWHERE ItemCode LIKE '[0-9][0-9][0-9][0-9]%' AND (ItemCode LIKE '[0-9][0-9][0-9][0-9]-[0-9][0-9][0-9][0-9]' OR ItemCode LIKE '[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]-[0-9][0-9]'). May be worth a try.
– GSerg
Nov 20 '18 at 16:44
|
show 3 more comments
3
It's theOR, I believe.
– GSerg
Nov 20 '18 at 16:38
3
look at the Query execution plan
– Cato
Nov 20 '18 at 16:41
regex can be pretty costly. Out of curiosity, how well does it perform if you have a where clause like this:isnumeric(replace(ItemCode, '-', '')) = 1? Additionally, will your ItemCode have a lot of non-numeric values?
– RToyo
Nov 20 '18 at 16:41
1
Does itemCode have an index ?
– Patrick Honorez
Nov 20 '18 at 16:44
It may or may not help if you doWHERE ItemCode LIKE '[0-9][0-9][0-9][0-9]%' AND (ItemCode LIKE '[0-9][0-9][0-9][0-9]-[0-9][0-9][0-9][0-9]' OR ItemCode LIKE '[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]-[0-9][0-9]'). May be worth a try.
– GSerg
Nov 20 '18 at 16:44
3
3
It's the
OR, I believe.– GSerg
Nov 20 '18 at 16:38
It's the
OR, I believe.– GSerg
Nov 20 '18 at 16:38
3
3
look at the Query execution plan
– Cato
Nov 20 '18 at 16:41
look at the Query execution plan
– Cato
Nov 20 '18 at 16:41
regex can be pretty costly. Out of curiosity, how well does it perform if you have a where clause like this:
isnumeric(replace(ItemCode, '-', '')) = 1? Additionally, will your ItemCode have a lot of non-numeric values?– RToyo
Nov 20 '18 at 16:41
regex can be pretty costly. Out of curiosity, how well does it perform if you have a where clause like this:
isnumeric(replace(ItemCode, '-', '')) = 1? Additionally, will your ItemCode have a lot of non-numeric values?– RToyo
Nov 20 '18 at 16:41
1
1
Does itemCode have an index ?
– Patrick Honorez
Nov 20 '18 at 16:44
Does itemCode have an index ?
– Patrick Honorez
Nov 20 '18 at 16:44
It may or may not help if you do
WHERE ItemCode LIKE '[0-9][0-9][0-9][0-9]%' AND (ItemCode LIKE '[0-9][0-9][0-9][0-9]-[0-9][0-9][0-9][0-9]' OR ItemCode LIKE '[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]-[0-9][0-9]'). May be worth a try.– GSerg
Nov 20 '18 at 16:44
It may or may not help if you do
WHERE ItemCode LIKE '[0-9][0-9][0-9][0-9]%' AND (ItemCode LIKE '[0-9][0-9][0-9][0-9]-[0-9][0-9][0-9][0-9]' OR ItemCode LIKE '[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]-[0-9][0-9]'). May be worth a try.– GSerg
Nov 20 '18 at 16:44
|
show 3 more comments
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53397525%2flike-0-9-much-slower-than-like%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53397525%2flike-0-9-much-slower-than-like%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
3
It's the
OR, I believe.– GSerg
Nov 20 '18 at 16:38
3
look at the Query execution plan
– Cato
Nov 20 '18 at 16:41
regex can be pretty costly. Out of curiosity, how well does it perform if you have a where clause like this:
isnumeric(replace(ItemCode, '-', '')) = 1? Additionally, will your ItemCode have a lot of non-numeric values?– RToyo
Nov 20 '18 at 16:41
1
Does itemCode have an index ?
– Patrick Honorez
Nov 20 '18 at 16:44
It may or may not help if you do
WHERE ItemCode LIKE '[0-9][0-9][0-9][0-9]%' AND (ItemCode LIKE '[0-9][0-9][0-9][0-9]-[0-9][0-9][0-9][0-9]' OR ItemCode LIKE '[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]-[0-9][0-9]'). May be worth a try.– GSerg
Nov 20 '18 at 16:44