CODEWITHSUNDEEP
sql-serverstored-proceduresstack-tracesql-server-profiler
deepz
deepz

Reputation: 225

SQL Profiler displaying stored procedure that doesn't exist

I have an automated service that runs 3 stored procedure namely sp_1, sp_2, sp_3. When I was running SQL Trace, it displayed the following results 

EXEC sp_1
EXEC sp_1
EXEC sp_2
EXEC sp_2
EXEC sp_4
EXEC sp_4
EXEC sp_2
EXEC sp_2

I don't know where the sp_4 came from. It doesn't exist in my automated service nor database.

Upvotes: 0

Views: 460

Answers (1)

TomTom
TomTom

Reputation: 62093

I know it sounds snippy, but who cares what is in the dababase?

The profiler shows what SQL gets executed. I can call in "EXEC funnybunny" and SQL Server will throw an error - AND the profiler will show that as being called.

So, in your case - stop looking at the database. Rather go to the application and look there why you call a SP that does not exist in the database. Look at the applicaiton layer (and the trace in more detail should tell you the call fails).

Upvotes: 1

Related Questions