June 1, 2011 at 12:04 pm
I'm looking for a few insights into this .....
Running a vendor application and in a trace I have many commands that look like this;
declare @p1 int set @p1=180150005 declare @p3 int set @p3=8 declare @p4 int set @p4=1 declare @p5 int set @p5=6 exec sp_ddopen @p1 output,N'sp_sproc_columns',@p3 output,@p4 output,@p5 output,N'sp[_]SOMENAMEHERE',NULL,NULL,NULL select @p1, @p3, @p4, @p5
and every day I have these two queries consuming a lot of the database time;
-- about 15% of total database activity
SELECT *
FROM #spproccol
-- another 15% with this procedure
sys.sp_sproc_columns
Can anyone offer some insight into this? What exactly creates this activity?
Thank you.
June 1, 2011 at 5:30 pm
Is it coded in the driver or application, i don't know, but it is a very bad practice to "discover" parameters of a known stored procedure. (or it is a product that "discovers" and explores objects of any db ? ).
June 1, 2011 at 6:15 pm
This is just the back end of a web application. I had read somewhere that this was the result of a command.parameters command in a .net application. Where the front end returns the expected parameters of a stored procedure but I'm looking for further details or confirmation. The parameters should be known.....
June 2, 2011 at 3:30 am
If anyone has a code example that would generate this command I would love to see it.
Thanks!
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply