current proc:
exec database.dbo.procname @parm1='A', @parm2='XC', @parm3='dv1', @parm4='CC', @parm5=date
the parms are all optional, if the proc is fired w/out parms, i am just returning top 50 from max date available

syntactically, what is the correct way to use sp_exeuctesql to fire this procedure, as opposed to simply exec ?
LVL 18
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Guy Hengel [angelIII / a3]Billing EngineerCommented:
you have to note the differences:

EXEC something
-> something needs to be a procedure name

EXEC ('sql')
-> will run the sql statement

exec sp_Executesql N'sql'
-> will run the sql statement

so, to run a procedure, you have only 1 option, unless you want to do like this:
exec sp_Executesql N' exec your_procedure '
which would be "nonsense"...

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ashish PatelCommented:
so you mean you want to execute a procedure using he sp_executesql ?
Ashish PatelCommented:
In other words: Why do you want to use sp_executesql here? Why not just execute the procedure, as

I agree with angelIII
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

dbaSQLAuthor Commented:
hmmm... ok.  then this is of no use.  i have a rather large table, against which only 1 procedure (aside from all my back end maintenance stuff) is run.  one day, all combinations of the optional parms come back lightening quick, perfectly.  the very next day, they come back 10 to 12 to 15 minutes greater in runtime.  next day, lighteninq quick yet again.  next day, runtimes are in the pooper.  
i figure it must be my indices, yet every single version of the proc I mentioned up there, when fired against the index tuning wizard against comes back saying
'No index recommendations for the workload and the chosen parameters.'

there is no fragmentation whatsoever, scan density is 100%, 'no indexes are recommended'
absolutely nothing is hitting this database except me
sp_who2 gives me no blkby, nothing runnable, everything quiet, so to speak
still, the procedure is taking for-freaking-ever to come back to me

so, i hit this page: http://www.sql-server-performance.com/tips/stored_procedures_p3.aspx
and am reading gup about the use of sp_executesql over EXEC

now, i'm not at all sure how to proceed

angelll, do you have any suggestions, or direction?
this is horribly, horribly pressing.  we put all this time into development, the proc was super, everything looked great, they deployed.  and now, nobody can use it, everybody is looking at me
dbaSQLAuthor Commented:
potentially i misinterpretted the read on sp_executesql.  that's the reason for this post.  still, are either of you able to advise?  be it indices, procedure, i'm not sure.  everything by itself looks fine.  but collectively, something is messing w/me now, and i cannot determine the reason for these hugely increased procedure runtimes
dbaSQLAuthor Commented:
well, my problem more than persists.  but, i think it is outside the sp_executesql bo, as you both have clarified for me.  i will award and close.
thank you for the input
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.