I just did a retest on my system and I can safely rename and un-rename the procs without any problems...

Whatever you did is most likely not a direct effect of...

Like I said, we're missing something real stupid.

Did you reset the permissions after creating the proc?

Try it, but I have a bad feeling we're missing something stupid...

Actually I would clear the proc cache for that db before doing a reboot... less drastic and might work.

Craig Farrell (3/2/2011)

---

Just curious, have you tried stopping and restarting the SQL Server Service, and/or rebooting the server? Smells like a glitch, so I'd start with doing standard glitch...

Close ssms, reopen.

Go to the db, procedures, select THAT procedure then delete.

Then use the script to recreate it.

Save a copy of the script. Then try manually deleting the proc and then recreate it. If it still doesn't work then something else has been changed in...

Have you tried exec dbo.sproc_NR_EWMDupVIN params.......?

Can you post the sp code here and how you are calling it?

Is it the same owner as the orignal?

Do you have the same name / owner as you have in the proc code?

Look at my code again. It's select * from dbname.owner.tblname

You need all 3. And if you need to use brackets then you need to close the brackets before...

Use my code. You'll just have to list all the columns you need compared in both queries instead of select *.

SELECT * FROM master.sys.objects

EXCEPT

SELECT * FROM msdb.sys.objects

How big are the diffs and log (avg daily).

I was first thinking unreleased spacefrom ntext or image datatypes. But it is being released so that can't be it (dbcc cleantable would have solved that).

The only real question...