I'm doing a happy dance, but I'm also kicking myself at the same time! (You're welcome for the visual.) 😛

There were two triggers running on the server, one that prevents table creation (unless you're a db admin) and one that prints a message when the dbo schema is not used. The stars were coming from the print statement of the schema-trigger. I should have known to check the triggers, but *assumed* that they were not enabled on our test server. If I had not tried to run the process authenticating as another user, I would not have gotten the following error:

[Execute SQL Task] Error: Executing the query "

/****** Object: Database [database] Script..." failed with the following error: "The transaction ended in the trigger. The batch has been aborted.

*************************************************************

If you need to Add/Delete/Modify a database on this server,

please contact the SQL DB Admin group.

---- Command not completed. ----

*************************************************************

Mail queued.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

The triggers were in my list of 110 objects that had *********s in them. Which means I would have eventually found it by disabeling the transfer of each of those 110 offending objects but I should have known to look at the triggers first!

I hope this might help someone avoid frustration in the future. 😀

Mods, if there's a way to mark this post as resolved, please do! 😎