Hi george.mamvura_406,
If your users belong to a windows group and you just added the group to be a SQL Server login, then it is a known issue and logged in the Release Notes.
http://sqloptimizersqlserver.inside.quest.com/themes/sqloptimizersqlserver/sbin/ReleaseNotes/QuestSQLOptimizerForSQLServer_ReleaseNotes.htm
There are 2 workarounds for the issue.
**1. Connect to the SQL Server with a login who has permission to create a user, and use the following script to create a user login (replace domainname\username with your NT login).
**
USE [yourdbname]
GO
CREATE USER [domainman\username] FOR LOGIN [domainname\username] WITH DEFAULT_SCHEMA=[dbo]
GO
After the above is created, connect to the database using Windows Authentication to use SQL Optimizer.
2. Contact your Database Administrator to directly add your domainuser as a login.
What is the version of your SQL Server?
MS SQL Server feedback forumn also mentioned this problem.
https://connect.microsoft.com/SQLServer/feedback/details/328585/default-schema-for-windows-group
SQL Server 2012 seems to have fixed the problem. When you connect to SQL Server 2012, there is no such problem.
Thanks,
Levin
