sure, default_schema only makes sense at the db level anyway. Just edit the properties of the user (which is your windows group) in the db you want and change the default_schema there.
Thanks, I was afraid of that. I have about 16 databases and four users in our development team (this is the dev system) that if I could change the group I would have less to do.
You can. That's what I meant. In the 16 databases, define the Windows group as a user, not the members of the group, Then change the default schema of that user
Tried that before the post. "The DEFAULT_SCHEMA clause cannot be used with a Windows group or with prinipals mapped to certificates or asymmetric keys. (Microsoft SQL Server, Error: 15259)"
To be able to that you need to upgrade to 2012 or higher. In 2008 R2 you have to create each individual user in each database to define a default schema for that user.