Using alternate database schemas

In SQL Server, Oracle and MySQL (among others) user logons are associated with a default “schema” that determines which tables and views they can see.

Users may have access to other tables and views that aren’t in their schema. When connecting to the database these tables will show up in the list, but when you try to get the list of fields you get an “Invalid object reference” error.

To reference these tables, use [Schema].[Table] for the table name to explicitly reference the table.

You can also change the user’s default schema on the server to the one matching the table.

A third option is to create a view under the user’s default schema that selects the necessary records.

At the present time you cannot enter [Schema].[Table] in the wizard, so if you need to use this workaround configure the job in the wizard and modify the table name in the old job options screen.