Comments
Sort by recent activity
Yes. Our operations group wants tight control over which accounts exist where, and what they can access - so autocreating users is right out.
Operations also manages the user accounts as a flat namespace (e.g. in addition to the domain, all Staging accounts start with 'Stage-'), so just eliminating the domain from the comparison isn't enough. The DB User being mapped is sufficient - though if it worked at the server level as well, that would be a nice-to-have.
Our company has a support contract, so if this needs to be made into a feature request through a different channel, I'm happy to write it up formally. It might take me a couple days to find time to list out the user stories and get the support contract details from the keeper of such things.
If it helps add priority points, I would expect that anyone using cloud-hosting for databases would find this feature useful as well. At least at one hosting provider (long in the past - I no longer remember the vendor), the user accounts were domain accounts assigned by the hoster, and matching the domain in a development environment was next to impossible.
Thanks,
-- Nate / comments
Yes. Our operations group wants tight control over which accounts exist where, and what they can access - so autocreating users is right out.
Operations also manages the user accounts as a flat nam...