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'.

Mojave Green Rattlesnake 1

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

1 answer

Mojave Green Rattlesnake 1 Reputation point

2021-02-09T21:31:18.013+00:00

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'
Please sign in to rate this answer.
Anurag Sharma 17,571 Reputation points

2021-02-10T04:49:35.253+00:00

Hi @Mojave Green Rattlesnake , 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'***.

Anurag Sharma 17,571 Reputation points

2021-02-17T05:50:10.077+00:00

Hi @Mojave Green Rattlesnake , you could mark your answer as accepted answer as that helped.

Mojave Green Rattlesnake 1 Reputation point

2021-02-17T18:23:51.003+00:00

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.

Anurag Sharma 17,571 Reputation points

2021-02-18T08:40:21.367+00:00

Hi @Mojave Green Rattlesnake , thanks for reverting back.

Normally drop with exists does not cause any issue but looks strange behavior and could be intermittent. I hope now that works as well.

Mojave Green Rattlesnake 1 Reputation point

2021-03-27T18:19:20.593+00:00

To catch the disappearing act of a sproc becoming a phantom in my assigned Azure 2014 SQL Server where sproc can't be identified (although it's in sys objects) I have implemented a second duplicate sproc for any sproc created which executes in the UI on the exception.

Thanks for sharing ideas.

All sprocs duplicated; peaceful so far. In car-speak like having spare rims and tires and brakes mounted inside to outer rims and tires and brakes.
Sign in to comment