question

MojaveGreenRattlesnake-5959 avatar image
0 Votes"
MojaveGreenRattlesnake-5959 asked MojaveGreenRattlesnake-5959 commented

Azure T-SQL Msg 2812, Level 16, State 1, Procedure dbo.myproc_stuff, Line 16 [Batch Start Line 144] Could not find stored procedure 'myproc_stuff'.

This odd behavior just started today after 3PM ET. This Azure T-SQL in Mgmt Studio v18.8 fails:

exec myproc_stuff 'this or that'

Whereas other stored procs execute A-OK. Plus sys.objects says myproc_stuff exists.

Azure Admin: What's going on?

Regards

G.

azure-sql-database
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

MojaveGreenRattlesnake-5959 avatar image
0 Votes"
MojaveGreenRattlesnake-5959 answered MojaveGreenRattlesnake-5959 commented

Well, progress, for some reason the previous sproc got caught in an Azure T-SQL black hole so this solution worked when I recreated the sproc as sproc2:

EXEC [dbo].[myproc_stuff2] 'this or that'

Instead of using the original:

EXEC [dbo].[myproc_stuff] 'this or that'

· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @MojaveGreenRattlesnake-5959, welcome to Microsoft Q&A forum.

Glad it worked out for you after recreating the stored procedure. Can you try renaming the original procedure and see if it works? You can rename the new one back to*'myproc_stuff'*.

0 Votes 0 ·

Hi @MojaveGreenRattlesnake-5959, you could mark your answer as accepted answer as that helped.

0 Votes 0 ·

Hi, Anurag, think you misunderstood me, I normally drop & create anyway. I tried my usual approximately 42 ways to retest the T-SQL. No, the result was the odd behavior which remains unanswered as to why it happened. Unexplained downtime. UDT. Luckily in alpha it was distressing to discover this after blowing a day.

Possible guess: perhaps drop with "exists" becomes dysfunctional in memory after awhile... (how long?, random right now) on the 2014 version SQL Server issued to my subscription.

0 Votes 0 ·
Show more comments