Create stored procedure that contains newlines with a oneliner sql statement





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty{ margin-bottom:0;
}






up vote
2
down vote

favorite












I want to put code in a single line that will create a stored procedure that contains newlines.




  • Is that possible?

  • Do I need to use sp_executesql?

  • How do I escape newlines in a sql statement?

  • How do I escape newlines in a string?










share|improve this question
























  • So you need to include carriage return and new line characters in your stored procedure, but not in your CREATE statement?
    – George.Palacios
    2 days ago










  • Yes, that is true.
    – Anders Lindén
    2 days ago






  • 2




    May we ask why?
    – user1008646
    2 days ago










  • To get one command per line resulting in a cleaner file.
    – Anders Lindén
    yesterday

















up vote
2
down vote

favorite












I want to put code in a single line that will create a stored procedure that contains newlines.




  • Is that possible?

  • Do I need to use sp_executesql?

  • How do I escape newlines in a sql statement?

  • How do I escape newlines in a string?










share|improve this question
























  • So you need to include carriage return and new line characters in your stored procedure, but not in your CREATE statement?
    – George.Palacios
    2 days ago










  • Yes, that is true.
    – Anders Lindén
    2 days ago






  • 2




    May we ask why?
    – user1008646
    2 days ago










  • To get one command per line resulting in a cleaner file.
    – Anders Lindén
    yesterday













up vote
2
down vote

favorite









up vote
2
down vote

favorite











I want to put code in a single line that will create a stored procedure that contains newlines.




  • Is that possible?

  • Do I need to use sp_executesql?

  • How do I escape newlines in a sql statement?

  • How do I escape newlines in a string?










share|improve this question















I want to put code in a single line that will create a stored procedure that contains newlines.




  • Is that possible?

  • Do I need to use sp_executesql?

  • How do I escape newlines in a sql statement?

  • How do I escape newlines in a string?







sql-server t-sql stored-procedures dynamic-sql






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited yesterday









Solomon Rutzky

47k579169




47k579169










asked 2 days ago









Anders Lindén

2211312




2211312












  • So you need to include carriage return and new line characters in your stored procedure, but not in your CREATE statement?
    – George.Palacios
    2 days ago










  • Yes, that is true.
    – Anders Lindén
    2 days ago






  • 2




    May we ask why?
    – user1008646
    2 days ago










  • To get one command per line resulting in a cleaner file.
    – Anders Lindén
    yesterday


















  • So you need to include carriage return and new line characters in your stored procedure, but not in your CREATE statement?
    – George.Palacios
    2 days ago










  • Yes, that is true.
    – Anders Lindén
    2 days ago






  • 2




    May we ask why?
    – user1008646
    2 days ago










  • To get one command per line resulting in a cleaner file.
    – Anders Lindén
    yesterday
















So you need to include carriage return and new line characters in your stored procedure, but not in your CREATE statement?
– George.Palacios
2 days ago




So you need to include carriage return and new line characters in your stored procedure, but not in your CREATE statement?
– George.Palacios
2 days ago












Yes, that is true.
– Anders Lindén
2 days ago




Yes, that is true.
– Anders Lindén
2 days ago




2




2




May we ask why?
– user1008646
2 days ago




May we ask why?
– user1008646
2 days ago












To get one command per line resulting in a cleaner file.
– Anders Lindén
yesterday




To get one command per line resulting in a cleaner file.
– Anders Lindén
yesterday










2 Answers
2






active

oldest

votes

















up vote
6
down vote













Yes, you can do something like this with dynamic SQL:



DECLARE @SQL NVARCHAR(MAX) = N'';
DECLARE @NewLine NCHAR(1) = NCHAR(10);

SET @SQL = @SQL + N'SELECT * ' + @NewLine + N'FROM sys.databases AS d ' + @NewLine + N'WHERE d.database_id > 4;' + @NewLine;

PRINT @SQL;
EXEC sys.sp_executesql @SQL;





share|improve this answer





















  • @AndersLindén yep, don't put a + before EXEC.
    – sp_BlitzErik
    2 days ago










  • I was trying to put the + in the argument to exec, building the sql string there
    – Anders Lindén
    2 days ago






  • 1




    @Anders um, why?
    – Aaron Bertrand
    2 days ago










  • The parameter of sp_executesql must be either a variable or a constant. No expressions allowed.
    – user1008646
    2 days ago










  • Is there no way of escaping characters in a t-sql string?
    – Anders Lindén
    2 days ago


















up vote
0
down vote













No, T-SQL cannot escape newlines, tabs, etc. It only has an escape sequence for embedded string delimiters: '' = '. There is also an escape sequence for delimited identifiers: either "" for ", or ]] for ], depending on which one is being used to delimit the identifier.



If you want to work with escape sequences, you can do so manually via the REPLACE function.



Depending on how the "single line of code" is being interpreted, you can do either:



IF (OBJECT_ID(N'tempdb..#TestProc') IS NOT NULL)
BEGIN
DROP PROCEDURE #TestProc;
END;
GO

-- The following is technically a single line (with multiple commands):
DECLARE @SQL NVARCHAR(MAX) = N'CREATE PROCEDURE #TestProcn(n @Param1 INT,n @Param2 NVARCHAR(128)n)nASnSET NOCOUNT ON;nnSELECT *nFROM tempdb.sys.sql_modulesnWHERE [object_id] = OBJECT_ID(N''tempdb..'' + @Param2);'; SET @SQL = REPLACE(@SQL, N'n', NCHAR(10)); EXEC (@SQL);

-- View the definition:
PRINT @SQL;

-- Test the proc:
EXEC #TestProc 2, N'#TestProc';


Or, if you can only execute a single command/statement, then you can try the following:



IF (OBJECT_ID(N'tempdb..#TestProc2') IS NOT NULL)
BEGIN
DROP PROCEDURE #TestProc2;
END;
GO

-- The following is a single line and a single statement:
EXEC (N'DECLARE @SQL NVARCHAR(MAX) = N''CREATE PROCEDURE #TestProc2n(n @Param1 INT,n @Param2 NVARCHAR(128)n)nASnSET NOCOUNT ON;nnSELECT *nFROM tempdb.sys.sql_modulesnWHERE [object_id] = OBJECT_ID(N''''tempdb..'''' + @Param2);''; SET @SQL = REPLACE(@SQL, N''n'', NCHAR(10)); EXEC (@SQL);');

-- Test the proc:
EXEC #TestProc2 2, N'#TestProc2';

-- View the definition:
DECLARE @SQL2 NVARCHAR(MAX);
SELECT @SQL2 = [definition]
FROM tempdb.sys.sql_modules
WHERE [object_id] = OBJECT_ID(N'tempdb..#TestProc2');

PRINT @SQL2;
-- returns (in "Messages" tab):
/*
CREATE PROCEDURE #TestProc2
(
@Param1 INT,
@Param2 NVARCHAR(128)
)
AS
SET NOCOUNT ON;

SELECT *
FROM tempdb.sys.sql_modules
WHERE [object_id] = OBJECT_ID(N'tempdb..' + @Param2);
*/





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',
    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%2f223095%2fcreate-stored-procedure-that-contains-newlines-with-a-oneliner-sql-statement%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    6
    down vote













    Yes, you can do something like this with dynamic SQL:



    DECLARE @SQL NVARCHAR(MAX) = N'';
    DECLARE @NewLine NCHAR(1) = NCHAR(10);

    SET @SQL = @SQL + N'SELECT * ' + @NewLine + N'FROM sys.databases AS d ' + @NewLine + N'WHERE d.database_id > 4;' + @NewLine;

    PRINT @SQL;
    EXEC sys.sp_executesql @SQL;





    share|improve this answer





















    • @AndersLindén yep, don't put a + before EXEC.
      – sp_BlitzErik
      2 days ago










    • I was trying to put the + in the argument to exec, building the sql string there
      – Anders Lindén
      2 days ago






    • 1




      @Anders um, why?
      – Aaron Bertrand
      2 days ago










    • The parameter of sp_executesql must be either a variable or a constant. No expressions allowed.
      – user1008646
      2 days ago










    • Is there no way of escaping characters in a t-sql string?
      – Anders Lindén
      2 days ago















    up vote
    6
    down vote













    Yes, you can do something like this with dynamic SQL:



    DECLARE @SQL NVARCHAR(MAX) = N'';
    DECLARE @NewLine NCHAR(1) = NCHAR(10);

    SET @SQL = @SQL + N'SELECT * ' + @NewLine + N'FROM sys.databases AS d ' + @NewLine + N'WHERE d.database_id > 4;' + @NewLine;

    PRINT @SQL;
    EXEC sys.sp_executesql @SQL;





    share|improve this answer





















    • @AndersLindén yep, don't put a + before EXEC.
      – sp_BlitzErik
      2 days ago










    • I was trying to put the + in the argument to exec, building the sql string there
      – Anders Lindén
      2 days ago






    • 1




      @Anders um, why?
      – Aaron Bertrand
      2 days ago










    • The parameter of sp_executesql must be either a variable or a constant. No expressions allowed.
      – user1008646
      2 days ago










    • Is there no way of escaping characters in a t-sql string?
      – Anders Lindén
      2 days ago













    up vote
    6
    down vote










    up vote
    6
    down vote









    Yes, you can do something like this with dynamic SQL:



    DECLARE @SQL NVARCHAR(MAX) = N'';
    DECLARE @NewLine NCHAR(1) = NCHAR(10);

    SET @SQL = @SQL + N'SELECT * ' + @NewLine + N'FROM sys.databases AS d ' + @NewLine + N'WHERE d.database_id > 4;' + @NewLine;

    PRINT @SQL;
    EXEC sys.sp_executesql @SQL;





    share|improve this answer












    Yes, you can do something like this with dynamic SQL:



    DECLARE @SQL NVARCHAR(MAX) = N'';
    DECLARE @NewLine NCHAR(1) = NCHAR(10);

    SET @SQL = @SQL + N'SELECT * ' + @NewLine + N'FROM sys.databases AS d ' + @NewLine + N'WHERE d.database_id > 4;' + @NewLine;

    PRINT @SQL;
    EXEC sys.sp_executesql @SQL;






    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered 2 days ago









    sp_BlitzErik

    20.6k1262102




    20.6k1262102












    • @AndersLindén yep, don't put a + before EXEC.
      – sp_BlitzErik
      2 days ago










    • I was trying to put the + in the argument to exec, building the sql string there
      – Anders Lindén
      2 days ago






    • 1




      @Anders um, why?
      – Aaron Bertrand
      2 days ago










    • The parameter of sp_executesql must be either a variable or a constant. No expressions allowed.
      – user1008646
      2 days ago










    • Is there no way of escaping characters in a t-sql string?
      – Anders Lindén
      2 days ago


















    • @AndersLindén yep, don't put a + before EXEC.
      – sp_BlitzErik
      2 days ago










    • I was trying to put the + in the argument to exec, building the sql string there
      – Anders Lindén
      2 days ago






    • 1




      @Anders um, why?
      – Aaron Bertrand
      2 days ago










    • The parameter of sp_executesql must be either a variable or a constant. No expressions allowed.
      – user1008646
      2 days ago










    • Is there no way of escaping characters in a t-sql string?
      – Anders Lindén
      2 days ago
















    @AndersLindén yep, don't put a + before EXEC.
    – sp_BlitzErik
    2 days ago




    @AndersLindén yep, don't put a + before EXEC.
    – sp_BlitzErik
    2 days ago












    I was trying to put the + in the argument to exec, building the sql string there
    – Anders Lindén
    2 days ago




    I was trying to put the + in the argument to exec, building the sql string there
    – Anders Lindén
    2 days ago




    1




    1




    @Anders um, why?
    – Aaron Bertrand
    2 days ago




    @Anders um, why?
    – Aaron Bertrand
    2 days ago












    The parameter of sp_executesql must be either a variable or a constant. No expressions allowed.
    – user1008646
    2 days ago




    The parameter of sp_executesql must be either a variable or a constant. No expressions allowed.
    – user1008646
    2 days ago












    Is there no way of escaping characters in a t-sql string?
    – Anders Lindén
    2 days ago




    Is there no way of escaping characters in a t-sql string?
    – Anders Lindén
    2 days ago












    up vote
    0
    down vote













    No, T-SQL cannot escape newlines, tabs, etc. It only has an escape sequence for embedded string delimiters: '' = '. There is also an escape sequence for delimited identifiers: either "" for ", or ]] for ], depending on which one is being used to delimit the identifier.



    If you want to work with escape sequences, you can do so manually via the REPLACE function.



    Depending on how the "single line of code" is being interpreted, you can do either:



    IF (OBJECT_ID(N'tempdb..#TestProc') IS NOT NULL)
    BEGIN
    DROP PROCEDURE #TestProc;
    END;
    GO

    -- The following is technically a single line (with multiple commands):
    DECLARE @SQL NVARCHAR(MAX) = N'CREATE PROCEDURE #TestProcn(n @Param1 INT,n @Param2 NVARCHAR(128)n)nASnSET NOCOUNT ON;nnSELECT *nFROM tempdb.sys.sql_modulesnWHERE [object_id] = OBJECT_ID(N''tempdb..'' + @Param2);'; SET @SQL = REPLACE(@SQL, N'n', NCHAR(10)); EXEC (@SQL);

    -- View the definition:
    PRINT @SQL;

    -- Test the proc:
    EXEC #TestProc 2, N'#TestProc';


    Or, if you can only execute a single command/statement, then you can try the following:



    IF (OBJECT_ID(N'tempdb..#TestProc2') IS NOT NULL)
    BEGIN
    DROP PROCEDURE #TestProc2;
    END;
    GO

    -- The following is a single line and a single statement:
    EXEC (N'DECLARE @SQL NVARCHAR(MAX) = N''CREATE PROCEDURE #TestProc2n(n @Param1 INT,n @Param2 NVARCHAR(128)n)nASnSET NOCOUNT ON;nnSELECT *nFROM tempdb.sys.sql_modulesnWHERE [object_id] = OBJECT_ID(N''''tempdb..'''' + @Param2);''; SET @SQL = REPLACE(@SQL, N''n'', NCHAR(10)); EXEC (@SQL);');

    -- Test the proc:
    EXEC #TestProc2 2, N'#TestProc2';

    -- View the definition:
    DECLARE @SQL2 NVARCHAR(MAX);
    SELECT @SQL2 = [definition]
    FROM tempdb.sys.sql_modules
    WHERE [object_id] = OBJECT_ID(N'tempdb..#TestProc2');

    PRINT @SQL2;
    -- returns (in "Messages" tab):
    /*
    CREATE PROCEDURE #TestProc2
    (
    @Param1 INT,
    @Param2 NVARCHAR(128)
    )
    AS
    SET NOCOUNT ON;

    SELECT *
    FROM tempdb.sys.sql_modules
    WHERE [object_id] = OBJECT_ID(N'tempdb..' + @Param2);
    */





    share|improve this answer

























      up vote
      0
      down vote













      No, T-SQL cannot escape newlines, tabs, etc. It only has an escape sequence for embedded string delimiters: '' = '. There is also an escape sequence for delimited identifiers: either "" for ", or ]] for ], depending on which one is being used to delimit the identifier.



      If you want to work with escape sequences, you can do so manually via the REPLACE function.



      Depending on how the "single line of code" is being interpreted, you can do either:



      IF (OBJECT_ID(N'tempdb..#TestProc') IS NOT NULL)
      BEGIN
      DROP PROCEDURE #TestProc;
      END;
      GO

      -- The following is technically a single line (with multiple commands):
      DECLARE @SQL NVARCHAR(MAX) = N'CREATE PROCEDURE #TestProcn(n @Param1 INT,n @Param2 NVARCHAR(128)n)nASnSET NOCOUNT ON;nnSELECT *nFROM tempdb.sys.sql_modulesnWHERE [object_id] = OBJECT_ID(N''tempdb..'' + @Param2);'; SET @SQL = REPLACE(@SQL, N'n', NCHAR(10)); EXEC (@SQL);

      -- View the definition:
      PRINT @SQL;

      -- Test the proc:
      EXEC #TestProc 2, N'#TestProc';


      Or, if you can only execute a single command/statement, then you can try the following:



      IF (OBJECT_ID(N'tempdb..#TestProc2') IS NOT NULL)
      BEGIN
      DROP PROCEDURE #TestProc2;
      END;
      GO

      -- The following is a single line and a single statement:
      EXEC (N'DECLARE @SQL NVARCHAR(MAX) = N''CREATE PROCEDURE #TestProc2n(n @Param1 INT,n @Param2 NVARCHAR(128)n)nASnSET NOCOUNT ON;nnSELECT *nFROM tempdb.sys.sql_modulesnWHERE [object_id] = OBJECT_ID(N''''tempdb..'''' + @Param2);''; SET @SQL = REPLACE(@SQL, N''n'', NCHAR(10)); EXEC (@SQL);');

      -- Test the proc:
      EXEC #TestProc2 2, N'#TestProc2';

      -- View the definition:
      DECLARE @SQL2 NVARCHAR(MAX);
      SELECT @SQL2 = [definition]
      FROM tempdb.sys.sql_modules
      WHERE [object_id] = OBJECT_ID(N'tempdb..#TestProc2');

      PRINT @SQL2;
      -- returns (in "Messages" tab):
      /*
      CREATE PROCEDURE #TestProc2
      (
      @Param1 INT,
      @Param2 NVARCHAR(128)
      )
      AS
      SET NOCOUNT ON;

      SELECT *
      FROM tempdb.sys.sql_modules
      WHERE [object_id] = OBJECT_ID(N'tempdb..' + @Param2);
      */





      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        No, T-SQL cannot escape newlines, tabs, etc. It only has an escape sequence for embedded string delimiters: '' = '. There is also an escape sequence for delimited identifiers: either "" for ", or ]] for ], depending on which one is being used to delimit the identifier.



        If you want to work with escape sequences, you can do so manually via the REPLACE function.



        Depending on how the "single line of code" is being interpreted, you can do either:



        IF (OBJECT_ID(N'tempdb..#TestProc') IS NOT NULL)
        BEGIN
        DROP PROCEDURE #TestProc;
        END;
        GO

        -- The following is technically a single line (with multiple commands):
        DECLARE @SQL NVARCHAR(MAX) = N'CREATE PROCEDURE #TestProcn(n @Param1 INT,n @Param2 NVARCHAR(128)n)nASnSET NOCOUNT ON;nnSELECT *nFROM tempdb.sys.sql_modulesnWHERE [object_id] = OBJECT_ID(N''tempdb..'' + @Param2);'; SET @SQL = REPLACE(@SQL, N'n', NCHAR(10)); EXEC (@SQL);

        -- View the definition:
        PRINT @SQL;

        -- Test the proc:
        EXEC #TestProc 2, N'#TestProc';


        Or, if you can only execute a single command/statement, then you can try the following:



        IF (OBJECT_ID(N'tempdb..#TestProc2') IS NOT NULL)
        BEGIN
        DROP PROCEDURE #TestProc2;
        END;
        GO

        -- The following is a single line and a single statement:
        EXEC (N'DECLARE @SQL NVARCHAR(MAX) = N''CREATE PROCEDURE #TestProc2n(n @Param1 INT,n @Param2 NVARCHAR(128)n)nASnSET NOCOUNT ON;nnSELECT *nFROM tempdb.sys.sql_modulesnWHERE [object_id] = OBJECT_ID(N''''tempdb..'''' + @Param2);''; SET @SQL = REPLACE(@SQL, N''n'', NCHAR(10)); EXEC (@SQL);');

        -- Test the proc:
        EXEC #TestProc2 2, N'#TestProc2';

        -- View the definition:
        DECLARE @SQL2 NVARCHAR(MAX);
        SELECT @SQL2 = [definition]
        FROM tempdb.sys.sql_modules
        WHERE [object_id] = OBJECT_ID(N'tempdb..#TestProc2');

        PRINT @SQL2;
        -- returns (in "Messages" tab):
        /*
        CREATE PROCEDURE #TestProc2
        (
        @Param1 INT,
        @Param2 NVARCHAR(128)
        )
        AS
        SET NOCOUNT ON;

        SELECT *
        FROM tempdb.sys.sql_modules
        WHERE [object_id] = OBJECT_ID(N'tempdb..' + @Param2);
        */





        share|improve this answer












        No, T-SQL cannot escape newlines, tabs, etc. It only has an escape sequence for embedded string delimiters: '' = '. There is also an escape sequence for delimited identifiers: either "" for ", or ]] for ], depending on which one is being used to delimit the identifier.



        If you want to work with escape sequences, you can do so manually via the REPLACE function.



        Depending on how the "single line of code" is being interpreted, you can do either:



        IF (OBJECT_ID(N'tempdb..#TestProc') IS NOT NULL)
        BEGIN
        DROP PROCEDURE #TestProc;
        END;
        GO

        -- The following is technically a single line (with multiple commands):
        DECLARE @SQL NVARCHAR(MAX) = N'CREATE PROCEDURE #TestProcn(n @Param1 INT,n @Param2 NVARCHAR(128)n)nASnSET NOCOUNT ON;nnSELECT *nFROM tempdb.sys.sql_modulesnWHERE [object_id] = OBJECT_ID(N''tempdb..'' + @Param2);'; SET @SQL = REPLACE(@SQL, N'n', NCHAR(10)); EXEC (@SQL);

        -- View the definition:
        PRINT @SQL;

        -- Test the proc:
        EXEC #TestProc 2, N'#TestProc';


        Or, if you can only execute a single command/statement, then you can try the following:



        IF (OBJECT_ID(N'tempdb..#TestProc2') IS NOT NULL)
        BEGIN
        DROP PROCEDURE #TestProc2;
        END;
        GO

        -- The following is a single line and a single statement:
        EXEC (N'DECLARE @SQL NVARCHAR(MAX) = N''CREATE PROCEDURE #TestProc2n(n @Param1 INT,n @Param2 NVARCHAR(128)n)nASnSET NOCOUNT ON;nnSELECT *nFROM tempdb.sys.sql_modulesnWHERE [object_id] = OBJECT_ID(N''''tempdb..'''' + @Param2);''; SET @SQL = REPLACE(@SQL, N''n'', NCHAR(10)); EXEC (@SQL);');

        -- Test the proc:
        EXEC #TestProc2 2, N'#TestProc2';

        -- View the definition:
        DECLARE @SQL2 NVARCHAR(MAX);
        SELECT @SQL2 = [definition]
        FROM tempdb.sys.sql_modules
        WHERE [object_id] = OBJECT_ID(N'tempdb..#TestProc2');

        PRINT @SQL2;
        -- returns (in "Messages" tab):
        /*
        CREATE PROCEDURE #TestProc2
        (
        @Param1 INT,
        @Param2 NVARCHAR(128)
        )
        AS
        SET NOCOUNT ON;

        SELECT *
        FROM tempdb.sys.sql_modules
        WHERE [object_id] = OBJECT_ID(N'tempdb..' + @Param2);
        */






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered yesterday









        Solomon Rutzky

        47k579169




        47k579169






























             

            draft saved


            draft discarded



















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f223095%2fcreate-stored-procedure-that-contains-newlines-with-a-oneliner-sql-statement%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

            Quarter-circle Tiles

            build a pushdown automaton that recognizes the reverse language of a given pushdown automaton?

            Mont Emei