SQL SSIS New File Connection Outputting to Unix (LF) and UCS-2 LE BOM Encoding












1















I'm using SQL 2014 64 bit on Windows Server 2012R2.



Whenever I perform package level logging using a File Connection Create File (not flat file) it is creating a file in Unix (LF) and UCS-2 LE BOM Encoding. I want it to be in Windows (CR LF) UTF-8 Encoding.



Why is this occurring? I have checked all regional settings and they all point to UKEnglish



Any ideas?



Thanks.










share|improve this question

























  • Any chance you have NFS (Network File System) installed on your Windows Server?

    – digital.aaron
    Nov 13 '18 at 20:32
















1















I'm using SQL 2014 64 bit on Windows Server 2012R2.



Whenever I perform package level logging using a File Connection Create File (not flat file) it is creating a file in Unix (LF) and UCS-2 LE BOM Encoding. I want it to be in Windows (CR LF) UTF-8 Encoding.



Why is this occurring? I have checked all regional settings and they all point to UKEnglish



Any ideas?



Thanks.










share|improve this question

























  • Any chance you have NFS (Network File System) installed on your Windows Server?

    – digital.aaron
    Nov 13 '18 at 20:32














1












1








1








I'm using SQL 2014 64 bit on Windows Server 2012R2.



Whenever I perform package level logging using a File Connection Create File (not flat file) it is creating a file in Unix (LF) and UCS-2 LE BOM Encoding. I want it to be in Windows (CR LF) UTF-8 Encoding.



Why is this occurring? I have checked all regional settings and they all point to UKEnglish



Any ideas?



Thanks.










share|improve this question
















I'm using SQL 2014 64 bit on Windows Server 2012R2.



Whenever I perform package level logging using a File Connection Create File (not flat file) it is creating a file in Unix (LF) and UCS-2 LE BOM Encoding. I want it to be in Windows (CR LF) UTF-8 Encoding.



Why is this occurring? I have checked all regional settings and they all point to UKEnglish



Any ideas?



Thanks.







sql-server visual-studio encoding ssis






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 13 '18 at 13:49









jarlh

29k52138




29k52138










asked Nov 13 '18 at 13:46









MichaelMichael

4651923




4651923













  • Any chance you have NFS (Network File System) installed on your Windows Server?

    – digital.aaron
    Nov 13 '18 at 20:32



















  • Any chance you have NFS (Network File System) installed on your Windows Server?

    – digital.aaron
    Nov 13 '18 at 20:32

















Any chance you have NFS (Network File System) installed on your Windows Server?

– digital.aaron
Nov 13 '18 at 20:32





Any chance you have NFS (Network File System) installed on your Windows Server?

– digital.aaron
Nov 13 '18 at 20:32












1 Answer
1






active

oldest

votes


















0














If it helps anyone else this is what worked in the end:




  • Uninstalled all Visual Studio Shell instances


  • Rebooted


  • Installed SSDT for VS 2017







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%2f53282442%2fsql-ssis-new-file-connection-outputting-to-unix-lf-and-ucs-2-le-bom-encoding%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














    If it helps anyone else this is what worked in the end:




    • Uninstalled all Visual Studio Shell instances


    • Rebooted


    • Installed SSDT for VS 2017







    share|improve this answer




























      0














      If it helps anyone else this is what worked in the end:




      • Uninstalled all Visual Studio Shell instances


      • Rebooted


      • Installed SSDT for VS 2017







      share|improve this answer


























        0












        0








        0







        If it helps anyone else this is what worked in the end:




        • Uninstalled all Visual Studio Shell instances


        • Rebooted


        • Installed SSDT for VS 2017







        share|improve this answer













        If it helps anyone else this is what worked in the end:




        • Uninstalled all Visual Studio Shell instances


        • Rebooted


        • Installed SSDT for VS 2017








        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 14 '18 at 9:09









        MichaelMichael

        4651923




        4651923






























            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%2f53282442%2fsql-ssis-new-file-connection-outputting-to-unix-lf-and-ucs-2-le-bom-encoding%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

            Full-time equivalent

            さくらももこ

            13 indicted, 8 arrested in Calif. drug cartel investigation