marc.snoeys (11/14/2012)
Apparently there is a view where one can query for possible problems when changing to a CONTAINED database: SYS.DM_DB_UNCONTAINED_ENTITIESBut a query on this view does not show this particular stored procedure.
I am not surprised. I would not expect the proc to be returned.
All in all: I guess I'm forced to use the COLLATE-clause ...
I think that is the correct move. Here is code that will be portable between both contained as well as non-contained databases regardless of which collation you are using in the database:
WHEN $action COLLATE DATABASE_DEFAULT = 'DELETE' THEN 'REMOVED'
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato