Access: Query and Append












-2















Question:



I'm running a huge query over a query and then appending it to a table. Is it really needed to run the prior queries or i can just convert the query with parameters to an append? save me the processing time of those two queries. I guess I'm trying to remove redundancy as per query it runs for like 15 minutes. Then the append runs the same.



Thanks.



-Al










share|improve this question

























  • What does VBA have to do with this question?

    – Cindy Meister
    Nov 20 '18 at 16:40











  • "Query over a query" - by this do you mean a sub query? If so, then no - you don't need to run the subquery before running the whole query. They Run together.

    – ArcherBird
    Nov 20 '18 at 16:40













  • Cindy Meister - Good catch! I've removed the VBA tag. My questions are usually vba related and became second nature. thanks!

    – Al5145
    Nov 20 '18 at 17:42











  • If you do the append, then a drop or delete the next time you run the append, I think you are guaranteed file bloat in the Access DBMS.

    – nicomp
    Nov 20 '18 at 19:17
















-2















Question:



I'm running a huge query over a query and then appending it to a table. Is it really needed to run the prior queries or i can just convert the query with parameters to an append? save me the processing time of those two queries. I guess I'm trying to remove redundancy as per query it runs for like 15 minutes. Then the append runs the same.



Thanks.



-Al










share|improve this question

























  • What does VBA have to do with this question?

    – Cindy Meister
    Nov 20 '18 at 16:40











  • "Query over a query" - by this do you mean a sub query? If so, then no - you don't need to run the subquery before running the whole query. They Run together.

    – ArcherBird
    Nov 20 '18 at 16:40













  • Cindy Meister - Good catch! I've removed the VBA tag. My questions are usually vba related and became second nature. thanks!

    – Al5145
    Nov 20 '18 at 17:42











  • If you do the append, then a drop or delete the next time you run the append, I think you are guaranteed file bloat in the Access DBMS.

    – nicomp
    Nov 20 '18 at 19:17














-2












-2








-2








Question:



I'm running a huge query over a query and then appending it to a table. Is it really needed to run the prior queries or i can just convert the query with parameters to an append? save me the processing time of those two queries. I guess I'm trying to remove redundancy as per query it runs for like 15 minutes. Then the append runs the same.



Thanks.



-Al










share|improve this question
















Question:



I'm running a huge query over a query and then appending it to a table. Is it really needed to run the prior queries or i can just convert the query with parameters to an append? save me the processing time of those two queries. I guess I'm trying to remove redundancy as per query it runs for like 15 minutes. Then the append runs the same.



Thanks.



-Al







ms-access append






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 20 '18 at 17:04







Al5145

















asked Nov 20 '18 at 16:21









Al5145Al5145

155




155













  • What does VBA have to do with this question?

    – Cindy Meister
    Nov 20 '18 at 16:40











  • "Query over a query" - by this do you mean a sub query? If so, then no - you don't need to run the subquery before running the whole query. They Run together.

    – ArcherBird
    Nov 20 '18 at 16:40













  • Cindy Meister - Good catch! I've removed the VBA tag. My questions are usually vba related and became second nature. thanks!

    – Al5145
    Nov 20 '18 at 17:42











  • If you do the append, then a drop or delete the next time you run the append, I think you are guaranteed file bloat in the Access DBMS.

    – nicomp
    Nov 20 '18 at 19:17



















  • What does VBA have to do with this question?

    – Cindy Meister
    Nov 20 '18 at 16:40











  • "Query over a query" - by this do you mean a sub query? If so, then no - you don't need to run the subquery before running the whole query. They Run together.

    – ArcherBird
    Nov 20 '18 at 16:40













  • Cindy Meister - Good catch! I've removed the VBA tag. My questions are usually vba related and became second nature. thanks!

    – Al5145
    Nov 20 '18 at 17:42











  • If you do the append, then a drop or delete the next time you run the append, I think you are guaranteed file bloat in the Access DBMS.

    – nicomp
    Nov 20 '18 at 19:17

















What does VBA have to do with this question?

– Cindy Meister
Nov 20 '18 at 16:40





What does VBA have to do with this question?

– Cindy Meister
Nov 20 '18 at 16:40













"Query over a query" - by this do you mean a sub query? If so, then no - you don't need to run the subquery before running the whole query. They Run together.

– ArcherBird
Nov 20 '18 at 16:40







"Query over a query" - by this do you mean a sub query? If so, then no - you don't need to run the subquery before running the whole query. They Run together.

– ArcherBird
Nov 20 '18 at 16:40















Cindy Meister - Good catch! I've removed the VBA tag. My questions are usually vba related and became second nature. thanks!

– Al5145
Nov 20 '18 at 17:42





Cindy Meister - Good catch! I've removed the VBA tag. My questions are usually vba related and became second nature. thanks!

– Al5145
Nov 20 '18 at 17:42













If you do the append, then a drop or delete the next time you run the append, I think you are guaranteed file bloat in the Access DBMS.

– nicomp
Nov 20 '18 at 19:17





If you do the append, then a drop or delete the next time you run the append, I think you are guaranteed file bloat in the Access DBMS.

– nicomp
Nov 20 '18 at 19:17












1 Answer
1






active

oldest

votes


















0














Assuming that the phrase "running a query over a query" means that you have a subquery within your Append query, then the answer is no: you do not need to separately run the subqueries before running the parent query.



Aside from the execution plan, no result data is stored by a query: the data is retrieved from the referenced tables each & every time the query is run.



Therefore, when you nest a query within another query, your parent query is not working with any saved results of prior evaluation of the nested query, but is evaluating the nested query as part of its own evaluation.






share|improve this answer























    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
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53397256%2faccess-query-and-append%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









    0














    Assuming that the phrase "running a query over a query" means that you have a subquery within your Append query, then the answer is no: you do not need to separately run the subqueries before running the parent query.



    Aside from the execution plan, no result data is stored by a query: the data is retrieved from the referenced tables each & every time the query is run.



    Therefore, when you nest a query within another query, your parent query is not working with any saved results of prior evaluation of the nested query, but is evaluating the nested query as part of its own evaluation.






    share|improve this answer




























      0














      Assuming that the phrase "running a query over a query" means that you have a subquery within your Append query, then the answer is no: you do not need to separately run the subqueries before running the parent query.



      Aside from the execution plan, no result data is stored by a query: the data is retrieved from the referenced tables each & every time the query is run.



      Therefore, when you nest a query within another query, your parent query is not working with any saved results of prior evaluation of the nested query, but is evaluating the nested query as part of its own evaluation.






      share|improve this answer


























        0












        0








        0







        Assuming that the phrase "running a query over a query" means that you have a subquery within your Append query, then the answer is no: you do not need to separately run the subqueries before running the parent query.



        Aside from the execution plan, no result data is stored by a query: the data is retrieved from the referenced tables each & every time the query is run.



        Therefore, when you nest a query within another query, your parent query is not working with any saved results of prior evaluation of the nested query, but is evaluating the nested query as part of its own evaluation.






        share|improve this answer













        Assuming that the phrase "running a query over a query" means that you have a subquery within your Append query, then the answer is no: you do not need to separately run the subqueries before running the parent query.



        Aside from the execution plan, no result data is stored by a query: the data is retrieved from the referenced tables each & every time the query is run.



        Therefore, when you nest a query within another query, your parent query is not working with any saved results of prior evaluation of the nested query, but is evaluating the nested query as part of its own evaluation.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 20 '18 at 17:44









        Lee MacLee Mac

        3,91131439




        3,91131439






























            draft saved

            draft discarded




















































            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53397256%2faccess-query-and-append%23new-answer', 'question_page');
            }
            );

            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







            Popular posts from this blog

            android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

            SQL update select statement

            'app-layout' is not a known element: how to share Component with different Modules