Miruna, thank you for noticing that. I knew it was something simple. I will make the change.

As for the Custom Query, I am working on one, but will need some time to create it. For now I will just use this one and once I have tested the Custom Query I will switch it over. Thank you again for your input.

So I'm guessing that the Insert Data activity does a simple Insert Into statement like the following:

USE databaseName
INSERT INTO databaseTable(column1, column2, column3)
VALUES ('value1', 'value2', 'value3');

And I'm guessing that the custom query you are suggesting would use a structure similar to this:

USE databaseName;
INSERT INTO databaseTable
VALUES
         ('value1','value2','value3'),
         ('value1','value2','value3'),
         ('value1','value2','value3')

How do you use the above structure to iterate through the values from the initial query from the other database in Workflow?

Not quite. See the link in my post above. It would be more like this (combining query data and insert data into one activity:

INSERT INTO table2
(column_name(s))
SELECT column_name(s)
FROM table1;

How would this work in Workflow if the data is coming from two different databases since in Workflow you have to select the Data Source and Database up front?

If they're on the same server, prefixing the tables with the database and schema name will still work in Custom Query, provided that the user specified in the datasource configuration has rights to read from the first DB and write to the second one.

INSERT INTO [database1].[schema1].[table1]

(column_name(s))

SELECT column_names(s)

FROM [database2].[schema2].[table2]