SQL Server profiler trace not showing parameter values





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I've searched for solutions on this but haven't found anything that works for me yet. I'm successfully using SQL Server Profiler to trace my calls to procedures and queries for one instance of SQL Server. It's very handy because I can see the calls to the procedures, including the values being passed in the parameters.



I am trying to do the same thing using a different instance of SQL Server and instead of seeing the values being passed in parameters, I'm seeing @parametername. I'm using the same install of SQL Server Profiler and I think I'm selecting the same trace settings (although for some reason the interface looks different when I connect to different instances).



Is there a setting inherent to the database instance itself that can be causing this or is it somehow a problem with my trace setup? I do have RPC:Completed checked. I really need to be able to see those values.



Thanks for any suggestions.










share|improve this question

























  • show this link: stackoverflow.com/a/1952890/1998051

    – Hamed Naeemaei
    Nov 16 '18 at 18:08











  • Thanks Hamed, I saw that link before. I also tried SQL: BatchCompleted SQL: BatchStarting SP:StmtStarting but no luck so far.

    – user2026318
    Nov 16 '18 at 19:09




















0















I've searched for solutions on this but haven't found anything that works for me yet. I'm successfully using SQL Server Profiler to trace my calls to procedures and queries for one instance of SQL Server. It's very handy because I can see the calls to the procedures, including the values being passed in the parameters.



I am trying to do the same thing using a different instance of SQL Server and instead of seeing the values being passed in parameters, I'm seeing @parametername. I'm using the same install of SQL Server Profiler and I think I'm selecting the same trace settings (although for some reason the interface looks different when I connect to different instances).



Is there a setting inherent to the database instance itself that can be causing this or is it somehow a problem with my trace setup? I do have RPC:Completed checked. I really need to be able to see those values.



Thanks for any suggestions.










share|improve this question

























  • show this link: stackoverflow.com/a/1952890/1998051

    – Hamed Naeemaei
    Nov 16 '18 at 18:08











  • Thanks Hamed, I saw that link before. I also tried SQL: BatchCompleted SQL: BatchStarting SP:StmtStarting but no luck so far.

    – user2026318
    Nov 16 '18 at 19:09
















0












0








0








I've searched for solutions on this but haven't found anything that works for me yet. I'm successfully using SQL Server Profiler to trace my calls to procedures and queries for one instance of SQL Server. It's very handy because I can see the calls to the procedures, including the values being passed in the parameters.



I am trying to do the same thing using a different instance of SQL Server and instead of seeing the values being passed in parameters, I'm seeing @parametername. I'm using the same install of SQL Server Profiler and I think I'm selecting the same trace settings (although for some reason the interface looks different when I connect to different instances).



Is there a setting inherent to the database instance itself that can be causing this or is it somehow a problem with my trace setup? I do have RPC:Completed checked. I really need to be able to see those values.



Thanks for any suggestions.










share|improve this question
















I've searched for solutions on this but haven't found anything that works for me yet. I'm successfully using SQL Server Profiler to trace my calls to procedures and queries for one instance of SQL Server. It's very handy because I can see the calls to the procedures, including the values being passed in the parameters.



I am trying to do the same thing using a different instance of SQL Server and instead of seeing the values being passed in parameters, I'm seeing @parametername. I'm using the same install of SQL Server Profiler and I think I'm selecting the same trace settings (although for some reason the interface looks different when I connect to different instances).



Is there a setting inherent to the database instance itself that can be causing this or is it somehow a problem with my trace setup? I do have RPC:Completed checked. I really need to be able to see those values.



Thanks for any suggestions.







sql-server query-analyzer






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 17 '18 at 2:42









Birel

497414




497414










asked Nov 16 '18 at 18:05









user2026318user2026318

466




466













  • show this link: stackoverflow.com/a/1952890/1998051

    – Hamed Naeemaei
    Nov 16 '18 at 18:08











  • Thanks Hamed, I saw that link before. I also tried SQL: BatchCompleted SQL: BatchStarting SP:StmtStarting but no luck so far.

    – user2026318
    Nov 16 '18 at 19:09





















  • show this link: stackoverflow.com/a/1952890/1998051

    – Hamed Naeemaei
    Nov 16 '18 at 18:08











  • Thanks Hamed, I saw that link before. I also tried SQL: BatchCompleted SQL: BatchStarting SP:StmtStarting but no luck so far.

    – user2026318
    Nov 16 '18 at 19:09



















show this link: stackoverflow.com/a/1952890/1998051

– Hamed Naeemaei
Nov 16 '18 at 18:08





show this link: stackoverflow.com/a/1952890/1998051

– Hamed Naeemaei
Nov 16 '18 at 18:08













Thanks Hamed, I saw that link before. I also tried SQL: BatchCompleted SQL: BatchStarting SP:StmtStarting but no luck so far.

– user2026318
Nov 16 '18 at 19:09







Thanks Hamed, I saw that link before. I also tried SQL: BatchCompleted SQL: BatchStarting SP:StmtStarting but no luck so far.

– user2026318
Nov 16 '18 at 19:09














1 Answer
1






active

oldest

votes


















0














You most probably don't have the same Events selected on the one SQL Instance, than on the other.



To achieve this, click on the Event Selection as can be seen below:



enter image description here



After selecting this, click on Show all events as can be seen below:



enter image description here



Compare the Event Selection with the one on the other Instance, then you'll be able to see.



Hope this helps.






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%2f53343184%2fsql-server-profiler-trace-not-showing-parameter-values%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














    You most probably don't have the same Events selected on the one SQL Instance, than on the other.



    To achieve this, click on the Event Selection as can be seen below:



    enter image description here



    After selecting this, click on Show all events as can be seen below:



    enter image description here



    Compare the Event Selection with the one on the other Instance, then you'll be able to see.



    Hope this helps.






    share|improve this answer




























      0














      You most probably don't have the same Events selected on the one SQL Instance, than on the other.



      To achieve this, click on the Event Selection as can be seen below:



      enter image description here



      After selecting this, click on Show all events as can be seen below:



      enter image description here



      Compare the Event Selection with the one on the other Instance, then you'll be able to see.



      Hope this helps.






      share|improve this answer


























        0












        0








        0







        You most probably don't have the same Events selected on the one SQL Instance, than on the other.



        To achieve this, click on the Event Selection as can be seen below:



        enter image description here



        After selecting this, click on Show all events as can be seen below:



        enter image description here



        Compare the Event Selection with the one on the other Instance, then you'll be able to see.



        Hope this helps.






        share|improve this answer













        You most probably don't have the same Events selected on the one SQL Instance, than on the other.



        To achieve this, click on the Event Selection as can be seen below:



        enter image description here



        After selecting this, click on Show all events as can be seen below:



        enter image description here



        Compare the Event Selection with the one on the other Instance, then you'll be able to see.



        Hope this helps.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 16 '18 at 19:33









        BirelBirel

        497414




        497414
































            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%2f53343184%2fsql-server-profiler-trace-not-showing-parameter-values%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

            Florida Star v. B. J. F.

            Error while running script in elastic search , gateway timeout

            Adding quotations to stringified JSON object values