I am running SQL Server Profiler (I am running because "Our user keep complaning application is running slow" so my first step,run SQL Server Profiler. Please correct me if i am wrong... Here i am checking which SP or query duration time is big Numbers. I pick one SP that has 223 Duration. I ran same SP in SSMS and execution is 0:00:00.
My question is should i worry about this store procedure?
2) Question:- Is it possible SP is running fine but .Net Programing is bad that's why application is slow? If yes is there any way i can Prove it SP is fine check .net Page?
Profiler is showing duration in milliseconds, so yes 223 milliseconds is less than one second.
Should you worry? Depends on what your performance requirements are.
Yes it's possible for the SP to run in SSMS but not fine from the application. Different connection parameters as well as how it's called can affect the execution plan.
You can duplicate what the code is doing by grabbing its connection parameters (you can get that in Profiler via the existing connections) and then grabbing the exact call (probably RPC:Completed). Now take the connection parameters and put them into an SSMS window and then add on the stored procedure call. See what you get regarding duration and execution plan.
You can also view the app's execution plan in Profiler.