Data catalogs connected to different SqlServer schemas

This could be a mistake with SqlServer Administration, but I have login users mapped to database users mapped to default schemas.
I have a Datalake flow parallel node featuring two Database conneciton points. When I add documents through the Object List, the table names will change based on the connection point's username (sqlserver login user), so I save the Database connection point. However, the Database connections wind up with the same values.
For example, when I select Database Connection Human Resources, I saved the username as "aw.humanresources" and saved the configuration.
Next I select Database Conneciton Persion, saved the username as "aw.person" and saved the configuration.
However, when I work with the documents I want to send to Datalake, both connection points are using "aw.person" and therefore connecting to same schema.

Find more posts tagged with

Infor Data Fabric

Accepted answers

All comments

Legacy Contributor

It appears that the ObjecList will only return Tables and Views located in the default schema. I created several synonyms that work with Management Studio and a simple jdbc client, but ObjectList will not recognize the synonyms. I also have several Stored Procedures in the same schema but they are not listed. Are Stored Procedures supported ?

I opened an Extreme incident on this matter.

Legacy Contributor

Just a quick gut check but presumably, both nodes in your Data Lake Flow are pointing to the correct respective connection point, correct? Or is that the bug you're encountering that both nodes end up pointing to the same connection point?

Stored procedures aren't yet supported but will be coming later in 2020. We also have an enhancement on supporting multi-schemas instead of only the default dbo. schema, for example.

Can you share your incident number with support?

Thanks much!

Legacy Contributor

Mike:

14177179

It sure looks the Document Flow Database connections use the same credentials, even though I am using a parallel node, I will build another flow.

The connection point's login id is definitely correct. If I change the mapped database user's schema, the ObjectList responds with the new Table/View list almost immediately, no complaints with performance.

I am fairly certain that SqlServer Logins require a Database User mapping. the Database User is assigned a Default Schema.

I have a hunch that your API is passing the schema it inherits from the database user default schema. Perhaps a senior SqlServer DBA will come across this thread, I would welcome their opinion on this matter. As it currently stands the modeler cannot join objects across SqlServer schemas; I have not tried this with other databases.

Copyright © 2025 Infor. All rights reserved.