After creating a new profile with SQL Server and integrated login (Windows authentication) in GT Datamaker and using it as a source, the following message pops up: The schema dbo was not found so will not be used.
The tables that are required as a source are not visible in GT Datamaker when opening a SQL Window.
When connecting directly to the same SQL Server database using SQL Server Management Studio, there is no problem viewing the required tables and using them in a query.
Also in Management Studio, the user has access to the dbo schema.
A different user configured with the same SQL Server permissions did not have the problem. For this user many different schemas are shown in the SQL Window in GT Datamaker.
The user with the problem only has one schema.
Under the settings menu, it was found that 'Current User Only' was ticked.
By running the following SQL Query it was confirmed that this was not a permission problem:
exec [sys].sp_tables N'',N'%',N'',N'',@fUsePattern=1;
This query showed all schemas.
Also under Settings -> View Connections it was possible to set any schema.
Explicitly setting the schema that had the tables (dbo) would show this schema and the required tables.
Under the settings menu, it was found that 'Current User Only' was ticked. After unticking this, the initial error 'The schema dbo was not found so will not be used.' no longer occurred and in a SQL window all schemas were shown.
All connection details for a particular connection can be found under: Settings -> View Connections.
For example: User ID, Schema and Profile
The i button at the bottom gives all debug connection details that can be saved in a file.
In this output the following is shown if 'Current User Only' is ticked: ib_current_schema_only = true