“SQL command” vs “Table or view” when importing entire tablesSSIS OLE DB Source Editor Data Access...

Manipulating a general length function

Why did Jodrell Bank assist the Soviet Union to collect data from their spacecraft in the mid 1960's?

1 0 1 0 1 0 1 0 1 0 1

How does Internet communication work on a coaxial cable?

Why did the villain in the first Men in Black movie care about Earth's Cockroaches?

What do you call a fact that doesn't match the settings?

Avoiding morning and evening handshakes

Issues with new Macs: Hardware makes them difficult for me to use. What options might be available in the future?

Getting a UK passport renewed when you have dual nationality and a different name in your second country?

Could flying insects re-enter the Earth's atmosphere from space without burning up?

How can I improve my fireworks photography?

Why don't I see the difference between two different files in insert mode in vim?

Why do neural networks need so many training examples to perform?

Jumping Numbers

What to do if authors don't respond to my serious concerns about their paper?

Everyone is beautiful

What is better: yes / no radio, or simple checkbox?

Unwarranted claim of higher degree of accuracy in zircon geochronology

Can you earn endless XP using a Flameskull and its self-revival feature?

How is the Incom shipyard still in business?

What makes the Forgotten Realms "forgotten"?

How can I deal with a significant flaw I found in my previous supervisor’s paper?

What's the most convenient time of year in the USA to end the world?

Using only 1s, make 29 with the minimum number of digits



“SQL command” vs “Table or view” when importing entire tables


SSIS OLE DB Source Editor Data Access Mode: “SQL command” vs “Table or view”ETL: extracting from 200 tables - SSIS data flow or custom T-SQL?sql agent job hangs without any errors or warningsSSIS OLEDB Command not firing triggersdecrypt data in column before load into destinationEncapsulate table with viewHow to create Dynamic table in stored procedure?SSIS changes SQL Server source data type from date to WSTRSSIS OLE DB Source Editor Data Access Mode: “SQL command” vs “Table or view”Writing Date as text in Excel using SSISPerformance Implications of encrypted data in a Clustered Columnstore Index













5















When using an OLEDB source editor, is there a performance benefit or difference in using "Sql Command" over "Table or View" when you want the entire table?



This is a variation on this question, in which the asker is talking about scenarios where they only want one or some columns in a table - in which case there is a benefit to using "Sql Command", as a select * from is still executed in the background when using "Table or View" even when columns are unticked.



I've also found this entry on the MSDN blog which states it is more efficient when looking at views due to the use of OpenRowset and a SET ROWCOUNT 1 which results in an inefficient query plan being cached and reused for the actual execution.



But if you're loading in a table and want every column, is there still an advantage to using the "Sql Command" option over "Table or View"?










share|improve this question














bumped to the homepage by Community 9 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Are you able to capture the SQL that is sent to the database with both options?

    – Joe Obbish
    Jun 25 '18 at 23:50
















5















When using an OLEDB source editor, is there a performance benefit or difference in using "Sql Command" over "Table or View" when you want the entire table?



This is a variation on this question, in which the asker is talking about scenarios where they only want one or some columns in a table - in which case there is a benefit to using "Sql Command", as a select * from is still executed in the background when using "Table or View" even when columns are unticked.



I've also found this entry on the MSDN blog which states it is more efficient when looking at views due to the use of OpenRowset and a SET ROWCOUNT 1 which results in an inefficient query plan being cached and reused for the actual execution.



But if you're loading in a table and want every column, is there still an advantage to using the "Sql Command" option over "Table or View"?










share|improve this question














bumped to the homepage by Community 9 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Are you able to capture the SQL that is sent to the database with both options?

    – Joe Obbish
    Jun 25 '18 at 23:50














5












5








5


1






When using an OLEDB source editor, is there a performance benefit or difference in using "Sql Command" over "Table or View" when you want the entire table?



This is a variation on this question, in which the asker is talking about scenarios where they only want one or some columns in a table - in which case there is a benefit to using "Sql Command", as a select * from is still executed in the background when using "Table or View" even when columns are unticked.



I've also found this entry on the MSDN blog which states it is more efficient when looking at views due to the use of OpenRowset and a SET ROWCOUNT 1 which results in an inefficient query plan being cached and reused for the actual execution.



But if you're loading in a table and want every column, is there still an advantage to using the "Sql Command" option over "Table or View"?










share|improve this question














When using an OLEDB source editor, is there a performance benefit or difference in using "Sql Command" over "Table or View" when you want the entire table?



This is a variation on this question, in which the asker is talking about scenarios where they only want one or some columns in a table - in which case there is a benefit to using "Sql Command", as a select * from is still executed in the background when using "Table or View" even when columns are unticked.



I've also found this entry on the MSDN blog which states it is more efficient when looking at views due to the use of OpenRowset and a SET ROWCOUNT 1 which results in an inefficient query plan being cached and reused for the actual execution.



But if you're loading in a table and want every column, is there still an advantage to using the "Sql Command" option over "Table or View"?







sql-server sql-server-2012 ssis ssis-2012






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jun 21 '18 at 14:46









KaiKai

1405




1405





bumped to the homepage by Community 9 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 9 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Are you able to capture the SQL that is sent to the database with both options?

    – Joe Obbish
    Jun 25 '18 at 23:50



















  • Are you able to capture the SQL that is sent to the database with both options?

    – Joe Obbish
    Jun 25 '18 at 23:50

















Are you able to capture the SQL that is sent to the database with both options?

– Joe Obbish
Jun 25 '18 at 23:50





Are you able to capture the SQL that is sent to the database with both options?

– Joe Obbish
Jun 25 '18 at 23:50










1 Answer
1






active

oldest

votes


















0














At one point in the product's past, selecting the table name from the drop down versus writing an explicit SELECT * FROM MyTable resulted in one fewer operation being performed. The table name selection did...something I can't reproduce now. It'd issue a command like though that resulted in a SELECT * but with an outer wrapper around it.



Profiler reports for 2014, it issued the command select * from [SB].[EventLog] A 2005/2008 instance would have indicated it did something like sp_somethingweird [SB].[EventLog]






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "182"
    };
    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: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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%2fdba.stackexchange.com%2fquestions%2f210267%2fsql-command-vs-table-or-view-when-importing-entire-tables%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














    At one point in the product's past, selecting the table name from the drop down versus writing an explicit SELECT * FROM MyTable resulted in one fewer operation being performed. The table name selection did...something I can't reproduce now. It'd issue a command like though that resulted in a SELECT * but with an outer wrapper around it.



    Profiler reports for 2014, it issued the command select * from [SB].[EventLog] A 2005/2008 instance would have indicated it did something like sp_somethingweird [SB].[EventLog]






    share|improve this answer




























      0














      At one point in the product's past, selecting the table name from the drop down versus writing an explicit SELECT * FROM MyTable resulted in one fewer operation being performed. The table name selection did...something I can't reproduce now. It'd issue a command like though that resulted in a SELECT * but with an outer wrapper around it.



      Profiler reports for 2014, it issued the command select * from [SB].[EventLog] A 2005/2008 instance would have indicated it did something like sp_somethingweird [SB].[EventLog]






      share|improve this answer


























        0












        0








        0







        At one point in the product's past, selecting the table name from the drop down versus writing an explicit SELECT * FROM MyTable resulted in one fewer operation being performed. The table name selection did...something I can't reproduce now. It'd issue a command like though that resulted in a SELECT * but with an outer wrapper around it.



        Profiler reports for 2014, it issued the command select * from [SB].[EventLog] A 2005/2008 instance would have indicated it did something like sp_somethingweird [SB].[EventLog]






        share|improve this answer













        At one point in the product's past, selecting the table name from the drop down versus writing an explicit SELECT * FROM MyTable resulted in one fewer operation being performed. The table name selection did...something I can't reproduce now. It'd issue a command like though that resulted in a SELECT * but with an outer wrapper around it.



        Profiler reports for 2014, it issued the command select * from [SB].[EventLog] A 2005/2008 instance would have indicated it did something like sp_somethingweird [SB].[EventLog]







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jun 27 '18 at 13:17









        billinkcbillinkc

        13.2k43775




        13.2k43775






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Database Administrators Stack Exchange!


            • 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%2fdba.stackexchange.com%2fquestions%2f210267%2fsql-command-vs-table-or-view-when-importing-entire-tables%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

            ORA-01691 (unable to extend lob segment) even though my tablespace has AUTOEXTEND onORA-01692: unable to...

            Always On Availability groups resolving state after failover - Remote harden of transaction...

            Circunscripción electoral de Guipúzcoa Referencias Menú de navegaciónLas claves del sistema electoral en...