none
The DEFAULT_SCHEMA clause cannot be used with a Windows group or with principals mapped to certificates or asymmetric keys.

    Question

  • I have a and ASP .Net DB on Sql 2008 which now needs to be situated on Sql 2005. I ran generate scripts to transfer the DB and contents over. When i ran the script all ran well except i received one error message:

    The DEFAULT_SCHEMA clause cannot be used with a Windows group or with principals mapped to certificates or asymmetric keys.

    Im not entirely sure if i can ignore this error or if i should attempt to do something with it to "fix" it. So could i ignore this error or what do i need to do in order to fix it. I dont want to ignore it if it means in future there may be a chance of an error.

    Thanks in advance.
    Friday, January 15, 2010 10:27 AM

Answers

  • Hello
    The cause of this issue is that SQL Compare and SQL Packager cannot reliably determine whether a Windows user is an actual user or a group. Windows groups can be mapped to SQL Server users just as Windows users, but a default schema cannot be specified for a Windows group. Unfortunately, not specifying a default schema for a Windows user can lead to other problems.

    The only possible workaround for this issue is to note the name of the group in the error dialog, and remove that SQL Server user from the synchronization.
    Regards RM Thirunavukkarasu MCP, MCITP http://thiruna.blog.com Please click the Mark as Answer button if a post solves your problem
    • Marked as answer by TheTerminator Monday, January 18, 2010 9:13 AM
    Saturday, January 16, 2010 7:18 AM
  • Very nice thread dealing with the same problem as yours
    http://social.msdn.microsoft.com/forums/en-US/sqlsecurity/thread/7d46a024-7ed5-4c9b-b091-3640dc04f5a1/ 
    Also make sure to follow the connect link in the above thread.
    Thanks, Leks
    • Marked as answer by TheTerminator Monday, January 18, 2010 9:13 AM
    Saturday, January 16, 2010 11:02 PM
    Answerer

All replies

  • Hello
    The cause of this issue is that SQL Compare and SQL Packager cannot reliably determine whether a Windows user is an actual user or a group. Windows groups can be mapped to SQL Server users just as Windows users, but a default schema cannot be specified for a Windows group. Unfortunately, not specifying a default schema for a Windows user can lead to other problems.

    The only possible workaround for this issue is to note the name of the group in the error dialog, and remove that SQL Server user from the synchronization.
    Regards RM Thirunavukkarasu MCP, MCITP http://thiruna.blog.com Please click the Mark as Answer button if a post solves your problem
    • Marked as answer by TheTerminator Monday, January 18, 2010 9:13 AM
    Saturday, January 16, 2010 7:18 AM
  • Very nice thread dealing with the same problem as yours
    http://social.msdn.microsoft.com/forums/en-US/sqlsecurity/thread/7d46a024-7ed5-4c9b-b091-3640dc04f5a1/ 
    Also make sure to follow the connect link in the above thread.
    Thanks, Leks
    • Marked as answer by TheTerminator Monday, January 18, 2010 9:13 AM
    Saturday, January 16, 2010 11:02 PM
    Answerer