Azure Managed Instance must suport all Collations
Azure Managed Instance must suport all Collations, not just SQL_Latin1_General_CP1_CI_AS Collation
Anonymous
shared this idea
Thank you for your feedback. Custom collations are currently in public preview: https://docs.microsoft.com/sql/relational-databases/collations/set-or-change-the-server-collation . Currently, you can use PowerShell/Azure ResourceManager template to create an instance with custom collation, while Portal support and more API will be available in January 2019.
4 comments
-
Dani Ljepava
commented
Collation is now supported for Managed Instance. The option can be seen whey you start the process of creating Managed Instance. It will apply to all databases created on Managed Instance. Please note that collation can be specified only at the creation of Managed Instance and that it cannot be updated at a subsequent time (unless a new Managed Instance is created).
-
Jan V.
commented
As far as I see, this is no longer an issue. When creating a managed SQL database or a new table, I can select several other COLLATION options (including 'Latin1_General_BIN2').
-
JocaPC
commented
Custom server-level collations are in preview - https://docs.microsoft.com/sql/relational-databases/collations/set-or-change-the-server-collation?view=sql-server-2017#setting-the-server-collation-in-managed-instance. Currently, you can set it using ARM template but soon we will support PowerShel & Portal
-
Andrei Ivanou
commented
Hi Team! Are there any updates? When to expect the promised collations support?