I'm using sp_rename to rename some tables in a production job. I really don't need it to issue warnings every time it's called. Maybe that made some kind of sense in SQL Server version 4.21, but why is the SP still issuing warnings at every use in this day and age?
(for that matter why isn't it a TSQL primitive at this point instead of an SP?)
Has anybody just taken the source out of master, dropped those warning messages, and used it happily ever after?
Thanks,
Josh