2812: Could not find stored procedure
SQL ServerWhat does it mean?
The stored procedure called with EXEC was not found in the current database/schema scope. No procedure exists with that name.
Why does it happen?
A typo in the procedure name, a missing or wrong schema prefix (e.g. dbo. omitted), the procedure being in a different database, not yet created, or not visible due to permissions.
How to fix it
Verify the procedure name and schema; use the fully qualified name in the call (e.g. EXEC dbo.ProcedureName). Make sure you are in the correct database (USE DatabaseName). Check that the procedure exists (sys.procedures / OBJECT_ID). Grant the required EXECUTE permission and verify that the deployment script ran.
More from this engine
- 512Subquery returned more than 1 value
- 207Invalid column name
- 156Incorrect syntax near the keyword
- 8623The query processor ran out of internal resources and could not produce a query plan
- 4104The multi-part identifier could not be bound
- 2714There is already an object named in the database
- 601Could not continue scan with NOLOCK due to data movement