Earlier I thought that it would not make sense to change the contents of the dbo-owner's procedures.
Is this correct behavior? |
This issue was fixed in December of 2015 and included in the v17 release. If a user owned a table or procedure with the same name as a system table or procedure (eg. a user with an “sa_split_list” procedure), that object would not be included if the databases was unloaded with dbunload. This has been fixed. Since the fix involves changes to the unload, upgrade, and database creation scripts, it will not be pushed back into existing branches. |
Seems like a bug to me...
FWIW: For the original dbo-owned objects, the doc page on the dbunload utitily states:
...so a modified dbo.xp_cmdshell would not be contained in the reload.sql file, but IMHO your DBA-owned one should be.