Prepared SQL query vs widening WHERE filter
I haven been working with R interfacing my Oracle DB using the DBI package. I read that preparing a query is often a good practice when trying to query the same statment different times.
My question is, assuming infinite RAM to accomodate for the data downloaded, which factors may influence in the different run times between two scenarios: running a prepared query N times or using a WHERE ... BETWEEN filter?
Let's say I have to run a query to analyze some time series information between 2012 and 2018. I have found different download times between running a prepared query for each month between my analysis window and just filtering the whole window.
sql r oracle odbc dbi
add a comment |
I haven been working with R interfacing my Oracle DB using the DBI package. I read that preparing a query is often a good practice when trying to query the same statment different times.
My question is, assuming infinite RAM to accomodate for the data downloaded, which factors may influence in the different run times between two scenarios: running a prepared query N times or using a WHERE ... BETWEEN filter?
Let's say I have to run a query to analyze some time series information between 2012 and 2018. I have found different download times between running a prepared query for each month between my analysis window and just filtering the whole window.
sql r oracle odbc dbi
add a comment |
I haven been working with R interfacing my Oracle DB using the DBI package. I read that preparing a query is often a good practice when trying to query the same statment different times.
My question is, assuming infinite RAM to accomodate for the data downloaded, which factors may influence in the different run times between two scenarios: running a prepared query N times or using a WHERE ... BETWEEN filter?
Let's say I have to run a query to analyze some time series information between 2012 and 2018. I have found different download times between running a prepared query for each month between my analysis window and just filtering the whole window.
sql r oracle odbc dbi
I haven been working with R interfacing my Oracle DB using the DBI package. I read that preparing a query is often a good practice when trying to query the same statment different times.
My question is, assuming infinite RAM to accomodate for the data downloaded, which factors may influence in the different run times between two scenarios: running a prepared query N times or using a WHERE ... BETWEEN filter?
Let's say I have to run a query to analyze some time series information between 2012 and 2018. I have found different download times between running a prepared query for each month between my analysis window and just filtering the whole window.
sql r oracle odbc dbi
sql r oracle odbc dbi
asked Nov 14 '18 at 17:05
André OviedoAndré Oviedo
114
114
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It depends on how the database optimizes your query. Maybe it chooses to optimize with an index when selecting just a single month, maybe it chooses to use a full table scan to retrieve the whole window at once.
Usually I would expect the query to retrieve the entire dataset at once to be more efficient than breaking it up in several parts per month.
Factors that play a role are, among others:
- What percentage of rows in the table are you accessing?
- Are there indexes that can be used?
- Which data was recently accessed (and might be cached)?
- How much data can the database handle/cache in memory?
- Did you use bind variables for the statements?
add a comment |
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%2f53305386%2fprepared-sql-query-vs-widening-where-filter%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It depends on how the database optimizes your query. Maybe it chooses to optimize with an index when selecting just a single month, maybe it chooses to use a full table scan to retrieve the whole window at once.
Usually I would expect the query to retrieve the entire dataset at once to be more efficient than breaking it up in several parts per month.
Factors that play a role are, among others:
- What percentage of rows in the table are you accessing?
- Are there indexes that can be used?
- Which data was recently accessed (and might be cached)?
- How much data can the database handle/cache in memory?
- Did you use bind variables for the statements?
add a comment |
It depends on how the database optimizes your query. Maybe it chooses to optimize with an index when selecting just a single month, maybe it chooses to use a full table scan to retrieve the whole window at once.
Usually I would expect the query to retrieve the entire dataset at once to be more efficient than breaking it up in several parts per month.
Factors that play a role are, among others:
- What percentage of rows in the table are you accessing?
- Are there indexes that can be used?
- Which data was recently accessed (and might be cached)?
- How much data can the database handle/cache in memory?
- Did you use bind variables for the statements?
add a comment |
It depends on how the database optimizes your query. Maybe it chooses to optimize with an index when selecting just a single month, maybe it chooses to use a full table scan to retrieve the whole window at once.
Usually I would expect the query to retrieve the entire dataset at once to be more efficient than breaking it up in several parts per month.
Factors that play a role are, among others:
- What percentage of rows in the table are you accessing?
- Are there indexes that can be used?
- Which data was recently accessed (and might be cached)?
- How much data can the database handle/cache in memory?
- Did you use bind variables for the statements?
It depends on how the database optimizes your query. Maybe it chooses to optimize with an index when selecting just a single month, maybe it chooses to use a full table scan to retrieve the whole window at once.
Usually I would expect the query to retrieve the entire dataset at once to be more efficient than breaking it up in several parts per month.
Factors that play a role are, among others:
- What percentage of rows in the table are you accessing?
- Are there indexes that can be used?
- Which data was recently accessed (and might be cached)?
- How much data can the database handle/cache in memory?
- Did you use bind variables for the statements?
answered Nov 15 '18 at 13:53
Martin SchapendonkMartin Schapendonk
8,78431324
8,78431324
add a comment |
add a comment |
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%2f53305386%2fprepared-sql-query-vs-widening-where-filter%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