unable to see entire SQL Statement in profiler

  • I ran profiler but the column textdata does not give me the entire sql statement.

    What is the reason?

    how to export entire textdata column?

    i did 2 way

    1)

    CREATE TABLE TraceResults (

    TextData VARCHAR(4000),

    Duration INT,

    Reads INT,

    Writes INT,

    CPU INT,

    StartTime DATETIME,

    EndTime DATETIME,

    ProcedureName VARCHAR(100)

    )

    Insert into TraceResults

    SELECT TextData, Duration, Reads, Writes, CPU, StartTime,EndTime

    FROM ::fn_trace_gettable('E:\tracename.trc',1)

    2) Open the trace file and save as Trace Table

    both did not gave me the entire Textdata. how can i get it, it limiting by 256 bytes

  • yuvipoy (5/7/2014)


    .....both did not gave me the entire Textdata. how can i get it, it limiting by 256 bytes

    This could be the default limit in SSMS. Look in SSMS for the "properties" option in the "tools" menu. Expand the tree for "Query results" and check the settings in the "results to grid" and "results to text".

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
  • HanShi (5/7/2014)


    yuvipoy (5/7/2014)


    .....both did not gave me the entire Textdata. how can i get it, it limiting by 256 bytes

    This could be the default limit in SSMS. Look in SSMS for the "properties" option in the "tools" menu. Expand the tree for "Query results" and check the settings in the "results to grid" and "results to text".

    I think you entered here wrongly.

    It is SQL server 200 it does not have SSMS.

    and thats too setting value in SSMS i dont think it will resolve.. in profiler 😉

  • I'm agree with you mate 🙂

    ______________

    fast weight loss pills, how to lose weight, slimming pills,cha de bugre

    🙂

  • yuvipoy (5/7/2014)


    I think you entered here wrongly.

    It is SQL server 200 it does not have SSMS.

    and thats too setting value in SSMS i dont think it will resolve.. in profiler 😉

    I'm sorry. I didn't notice this thread was under the SQL2000 forum.

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply