Option to normalize casing of identifiers in the ScriptGenerator

まず ScriptGenerator と現在の設定を特定し、次に生成された SQL で識別子がどのように出力されるかを追跡します。大文字と小文字の扱いが一律に適用されるのか、それともインスタンスレベルとデータベースレベルで個別の設定が必要なのかを確認します。完了の条件は、PreserveOriginal がデフォルトのままであり、LowerCase と UpperCase が指定どおりに不変の大文字・小文字変換を使用することです。

SQL Server compares identifiers with respect to the CI/CS, AI/AS setting of the respective database's collation. While accent sensitivity has no effect on the SQL source code, case-sensitivity may have such an effect when the goal is to produce a 'canonical' form of the source code. The locale part of the collation plays no part in this.

Hence, the settings of the ScriptGenerator should be extended with an option to normalize casing of identifiers as follows:

• PreserveOriginal — outputs identifiers as-is; this shall be the default behavior corresponding to the current state (no breaking change)
• LowerCase — lower-case all identifiers when producing the output
• UpperCase — upper-case all identifiers when producing the output

A simple ToLowerInvariant() / ToUpperInvariant() should be used.

Question is, whether the ScriptGenerator should support separate settings for instance-level (global) objects versus objects in a database. This would significantly increase the complexity. See also Database identifiers:

The collation of an identifier depends on the level at which it's defined. Identifiers of instance-level objects, such as logins and database names, are assigned the default collation of the instance. Identifiers of objects in a database, such as tables, views, and column names, are assigned the default collation of the database.