Keep in mind that this technique works only because there is a bug in SSMS. If that bug is ever fixed, then this work-around will likely stop working. It might be a good ideaPlease see the "UPDATE" section at the bottom for links to add athe bug report I filed about this, as well as the enhancement suggestion over at https://feedback.azure.com/forums/908035-sql-serverI filed requesting a "case-insensitive" check-box on the "Filter Settings" dialog :-), per filterable property.
From Randi's answer:
Well, it depends. There are two levels of collations — instance-level and database-level — and the one that matters depends on what meta-data someone is trying to filter. Instance-level collation affects filtering instance-level meta data (e.g. Logins, Linked Servers, etc) and meta data in system databases. Database-level collation affects filtering user database meta data (e.g. Users, Tables, etc). In a Contained / Partially-Contained database, filtering the database-level meta data will always use the collation: Latin1_General_100_CI_AS_WS_KS_SC
.
UPDATE
I have submitted the following feedback items to Microsoft: