analysing Profiler trace

  • "declare @P1 int set @P1=180150126 declare @P2 int set @P2=1 declare @P3 int set @P3=4 declare @P4 int set @P4=158 exec sp_cursorexecute 156, @P1 output, @P2 output, @P3 output, @P4 output select @P1, @P2, @P3, @P4",65,15343,1187,NULL

    "declare @P1 int set @P1=8259 declare @P2 int set @P2=180171758 declare @P3 int set @P3=1 declare @P4 int set @P4=4 declare @P5 int set @P5=7 exec sp_cursorprepexec @P1 output, @P2 output, N'@P1 datetime,@P2 datetime,@P3 int,@P4 int,@P5 int', N'SELECT JOB.J",62,12626,922,NULL

    "declare @P1 int set @P1=8261 declare @P2 int set @P2=180171760 declare @P3 int set @P3=1 declare @P4 int set @P4=4 declare @P5 int set @P5=7 exec sp_cursorprepexec @P1 output, @P2 output, N'@P1 datetime,@P2 datetime,@P3 int,@P4 int,@P5 int', N'SELECT JOB.J",62,10940,1109,NULL

    "declare @P1 int set @P1=8211 declare @P2 int set @P2=180171662 declare @P3 int set @P3=1 declare @P4 int set @P4=4 declare @P5 int set @P5=7 exec sp_cursorprepexec @P1 output, @P2 output, N'@P1 datetime,@P2 datetime,@P3 int,@P4 int,@P5 int', N'SELECT JOB.J",62,8733,1047,NULL

    "declare @P1 int set @P1=8264 declare @P2 int set @P2=180171767 declare @P3 int set @P3=1 declare @P4 int set @P4=4 declare @P5 int set @P5=7 exec sp_cursorprepexec @P1 output, @P2 output, N'@P1 datetime,@P2 datetime,@P3 int,@P4 int,@P5 int', N'SELECT JOB.J",62,6830,936,NULL

    "declare @P1 int set @P1=8059 declare @P2 int set @P2=180171393 declare @P3 int set @P3=1 declare @P4 int set @P4=4 declare @P5 int set @P5=110 exec sp_cursorprepexec @P1 output, @P2 output, N'@P1 datetime,@P2 datetime,@P3 int,@P4 int,@P5 int', N'SELECT JOB",62,5296,1046,NULL

    "declare @P1 int set @P1=8147 declare @P2 int set @P2=180171545 declare @P3 int set @P3=1 declare @P4 int set @P4=4 declare @P5 int set @P5=1 exec sp_cursorprepexec @P1 output, @P2 output, N'@P1 datetime,@P2 datetime,@P3 int,@P4 int,@P5 int', N'SELECT JOB.J",62,5266,985,NULL

    "declare @P1 int set @P1=8209 declare @P2 int set @P2=180171660 declare @P3 int set @P3=1 declare @P4 int set @P4=4 declare @P5 int set @P5=8 exec sp_cursorprepexec @P1 output, @P2 output, N'@P1 datetime,@P2 datetime,@P3 int,@P4 int,@P5 int', N'SELECT JOB.J",62,4063,1062,NULL

    "declare @P1 int set @P1=8144 declare @P2 int set @P2=180171538 declare @P3 int set @P3=1 declare @P4 int set @P4=4 declare @P5 int set @P5=1 exec sp_cursorprepexec @P1 output, @P2 output, N'@P1 datetime,@P2 datetime,@P3 int,@P4 int,@P5 int', N'SELECT JOB.J",62,4046,1906,NULL

    "declare @P1 int set @P1=8105 declare @P2 int set @P2=180171470 declare @P3 int set @P3=1 declare @P4 int set @P4=4 declare @P5 int set @P5=36 exec sp_cursorprepexec @P1 output, @P2 output, N'@P1 datetime,@P2 datetime,@P3 int,@P4 int,@P5 int', N'SELECT JOB.",62,3906,985,NULL

    "declare @P1 int set @P1=180150130 declare @P2 int set @P2=1 declare @P3 int set @P3=4 declare @P4 int set @P4=158 exec sp_cursorexecute 157, @P1 output, @P2 output, @P3 output, @P4 output select @P1, @P2, @P3, @P4",65,3703,1126,NULL

    "declare @P1 int set @P1=8207 declare @P2 int set @P2=180171658 declare @P3 int set @P3=1 declare @P4 int set @P4=4 declare @P5 int set @P5=8 exec sp_cursorprepexec @P1 output, @P2 output, N'@P1 datetime,@P2 datetime,@P3 int,@P4 int,@P5 int', N'SELECT JOB.J",62,3656,937,NULL

    "declare @P1 int set @P1=8064 declare @P2 int set @P2=180171398 declare @P3 int set @P3=1 declare @P4 int set @P4=4 declare @P5 int set @P5=40 exec sp_cursorprepexec @P1 output, @P2 output, NULL, N'SELECT JOB.JOBID,JOB.COMPANYID,JOB.SITEID,JOB.JOBNUMBER,JOB",62,3110,1110,NULL

    "declare @P1 int set @P1=8142 declare @P2 int set @P2=180171536 declare @P3 int set @P3=1 declare @P4 int set @P4=4 declare @P5 int set @P5=9 exec sp_cursorprepexec @P1 output, @P2 output, NULL, N'SELECT JOB.JOBID,JOB.COMPANYID,JOB.SITEID,JOB.JOBNUMBER,JOB.",62,3063,1906,NULL

    "declare @P1 int set @P1=8462 declare @P2 int set @P2=180172095 declare @P3 int set @P3=1 declare @P4 int set @P4=4 declare @P5 int set @P5=7 exec sp_cursorprepexec @P1 output, @P2 output, N'@P1 datetime,@P2 datetime,@P3 int,@P4 int,@P5 int', N'SELECT JOB.J",62,2856,954,NULL

    "declare @P1 int set @P1=7753 declare @P2 int set @P2=180170687 declare @P3 int set @P3=1 declare @P4 int set @P4=4 declare @P5 int set @P5=158 exec sp_cursorprepexec @P1 output, @P2 output, NULL, N'SELECT JOB.JOBID,JOB.COMPANYID,JOB.SITEID,JOB.JOBNUMBER,JO",62,2720,1110,NULL

    "declare @P1 int set @P1=7754 declare @P2 int set @P2=180170688 declare @P3 int set @P3=1 declare @P4 int set @P4=4 declare @P5 int set @P5=110 exec sp_cursorprepexec @P1 output, @P2 output, NULL, N'SELECT JOB.JOBID,JOB.COMPANYID,JOB.SITEID,JOB.JOBNUMBER,JO",62,2576,2203,NULL

    I am posting my profiler trace output.

    If you notice there is call made to

    sp_cursorprepexec &

    sp_cursorexecute

    Does anybody know what these stor proc's are..?

    Any advise will be appreciated..

    Many thanks

    "declare @P1 int set @P1=8491 declare @P2 int set @P2=180172137 declare @P3 int set @P3=1 declare @P4 int set @P4=4 declare @P5 int set @P5=7 exec sp_cursorprepexec @P1 output, @P2 output, N'@P1 datetime,@P2 datetime,@P3 int,@P4 int,@P5 int', N'SELECT JOB.J",62,2530,1000,NULL

    "declare @P1 int set @P1=8104 declare @P2 int set @P2=180171469 declare @P3 int set @P3=1 declare @P4 int set @P4=4 declare @P5 int set @P5=5 exec sp_cursorprepexec @P1 output, @P2 output, N'@P1 datetime,@P2 datetime,@P3 int,@P4 int,@P5 int', N'SELECT JOB.J",62,2453,859,NULL

    "declare @P1 int set @P1=8101 declare @P2 int set @P2=180171466 declare @P3 int set @P3=1 declare @P4 int set @P4=4 declare @P5 int set @P5=5 exec sp_cursorprepexec @P1 output, @P2 output, N'@P1 datetime,@P2 datetime,@P3 int,@P4 int,@P5 int', N'SELECT JOB.J",62,2076,1000,NULL

  • What is this client doing to access the server? Most likely this is a translation of an ADO/ADO.NET function.

  • The client is using SQL 2000 and uses a program called Clarion to connect to the database.

  • I've seen with a client that used jdbc. I haven't found an easy way of identifying the commands run. From what I have found, the sp_cursorprepexec has the statement in it, and the cursorexecute runs the statement. Is a right pain to analyse unfortunatly.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

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

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