Creating a Materialized View

[huber1]

According to the documentation for creating a materialized view, the sort_collation setting must be Internal. I have set it to the ID 51 to get the proper sorting for Umlaute. Now I am wondering if there is a way to set this opion to Internal and still have the sort collation behave like if I had set it to 51?

(SQL Anywhere 12, Version 12.0.1.4201).

Regards, Robert

[VolkerBarth]

In my understanding, there's no problem in either setting the sort_collation temporarily to a different setting or to explicitly use SORTKEY(MyColumn, MySortCollation) when you run queries against the mat. view. However, the drawback might be that the mat. view won't be used automatically by the optimizer when you do not refer to it in your queries - that's my understanding of the phrase "for the view to be used by the optimizer" from the v12.0.1 docs which state:

The following database options must have the specified settings when a materialized view is created; otherwise, an error is returned. These database option values are also required for the view to be used by the optimizer:

• ansinull=On
  [...]
• sort_collation=Internal

[huber1]

I would assume there must be a setting where it is possible to create a mat. view without changing the setting (options) to create the mat. view and then switch back to the sort_collation ID 51 (in my case). But I really don't know.