Sql server enable contained database

Hi, we have a third party that needs enable contained database to be enabled…I have created a databse and provide the necessary permissions for them. But they want this to be enabled. It seems that normally it used for developers to migrate databases from one server to another. But this doesn’t concern us. Is there any other reason they would want this? They are saying that their scripts cannot be used to populate the database otherwise. This setting is at the instance level. Dont know if this has implications .etc.

Thanks in advance

My first guess is that’s it to cover their own ass. So anything they’re doing to “their” DB, can’t affect any of “your” DB’s. And vice versa.

The following might give you more insight

True, but permissions have been set so they cannot access any other databases. This is a live production server so dont know what the implications are of setting it on the fly

To play devil’s advocate …

What if those permissions aren’t set properly?
What about tasks run by the system - like maintenance plans. Could a maintenance plan setup to be run on “your” DB be also run on “their” DB?

And I completely understand your hesitation to switch on a feature that could affect your production DB.

Thanks

Especially as it came up 5 mins before the install…

1 Like