|
|
Posted by John Bell on 09/13/05 23:50
Hi
sp_executesql is documented in BOL the first parameter is a Unicode string
to be executed. you may want to run SQL profiler to find out what the
commands are.
John
"rcamarda" <rcamarda@cablespeed.com> wrote in message
news:1126614746.141363.266270@f14g2000cwb.googlegroups.com...
> Hello,
> Our SQL machine is getting bogged down by some sort of stored procedure
> and I am trying to find which one. My SQLdiagnostic software (by Idera)
> that monitors our SQL server, says that these commands are executing
> and taking upwards of 30 minutes to run. This is new and unexpected.
>
> The commands are:
>
> exec sp_executesql @Pm0 = 0x683AAD4E8159A84C90B65216A4DA25DE, @Pm1 =
> 25, @Pm2 = 2, @Pm3 = 1
> exec sp_executesql @Pm0 = 0x683AAD4E8159A84C90B65216A4DA25DE, @Pm1 =
> 105, @Pm2 = 2, @Pm3 = 1
> exec sp_executesql @Pm0 = 0x683AAD4E8159A84C90B65216A4DA25DE, @Pm1 =
> 57, @Pm2 = 2, @Pm3 = 1
>
> I am getting pages of these and yesterday the are taking upto 30
> minutes to run (currently they are taking 1-2 minutes to complete w/o
> people on the machine).
>
> We are not getting much help from our software vendor (of our
> admissions software, not Idera) on this matter. I have sa access to the
> SQL machine and I can see the pages and pages of stored procedures, but
> I don't know what the above is running. I want to find the stored
> procedure that keeps getting executed. Is the @Pm0 = an encrypted
> entry?
>
> Any advice I would appreciate.
> Thanks
> Rob Camarda
>
Navigation:
[Reply to this message]
|