It seems that the workbench doesn't correctly cope with aliases in a datastore. See the image below:
In the deployed job, the alias is correctly setup in the datastore as well as the dataflow target tables as shown below.
However, the creation script isn't right. It is putting the alias name as a hardcoded owner name as seen below:
This of course results in a crashed ETL job as that user "DS_OWNER" doesn't actually exist in SQL Server. To make matters worse, if I create a datastore without an alias, Workbench uses the datastore's username as an owner name! (I have noted that this bug is in other threads).
The only workaround I can see using is:
1) Create a target datastore and do not use aliases.
2) Specify the target owner as "DBO" in the replication job.
Seems like another bug - the third issue I've run into today! Can anyone advise?
Thanks!
Bob