SQL Prompt Smart Rename is an abysmal failure for me thus far? What is up with transactions??
I have to rename a field in a table.
I've used Smart Rename thinking this will do the trick, but the script fails every time.
It fails because the rename of the column on the table isn't "known" or "seen" by subsequent scripts to change views/sp's.
It's all inside a giant transaction, and those items all fail, every single time.
I see that 12 years ago Smart Rename had some issues, and they seem to still exist in the current version?
I need help here - do I just take away the transaction (and again from 2007, there was to be a version where we could turn off using a transaction, but it doesn't exist yet) code?