If you have selected the Validate Code Page option, the Collation tab
only displays the collation descriptions that are supported by the operating system that
is installed on the client computer that is being used to create the database. That is to
say it displays those collations that match either the OEM or ANSI code pages that are
used by the client computer. If you have not selected the Validate Code Page option,
the Collation tab displays all the available collations.
If you select Windows Collation, you should choose a collation that matches your
geographic location/language needs as closely as possible. The binary, casesensitive
and accent-sensitive properties of the collation that you select can be
modified. Selecting Binary will clear both the Case-sensitive and Accent-sensitive
properties. Selecting either the Case-sensitive or Accent-sensitive properties will
clear the Binary property. Use the AssistButton h to see the Windows collation
descriptions that are available.
When you select SQL Collation, the binary, case-sensitive and accent-sensitive
properties are inactive because they are included in the collation description and you
should choose a collation description that matches your code page and the required
binary/dictionary and case-/accent-sensitive characteristics. Use the AssistButton h to
see the SQL collation descriptions that are available.
Each new database you create can use a different collation. After the database has
been created, you can change the collation that it uses by clicking File, Database,
Alter. For more information about altering the database and changing the collation,
The Collation tab also contains an option called Validate Code Page. This option is
selected by default. If this option is selected, every time a client connects to the
database the OEM or ANSI code page that is used by the client computer is checked
to make sure that it is compatible with the code page used by the database. If this
option is not selected, the code page that is used by the client computers is not
validated.
You can disable this option if you are sure that every character is converted correctly
between all the clients and the database. Disabling this setting allows clients that are
using different regional settings (code pages) to use the same database even though
some characters entered by one client may not be interpreted correctly by another
client or by the server.
Other problems that can be caused by not validating the code page are:
· The sorting of textual data is governed by the database server and this means that
the data may not be sorted according to the rules specified on the "incompatible"
client computers. This problem will be more acute if there is some C/AL code that
only works correctly when a particular sort order is selected.
· If you are accessing SQL Server with external tools, these tools may not be able to
read the data that has been entered by the "incompatible" clients correctly.
We therefore recommend that you use the default setting and validate code pages
because this will avoid all these problems.
For more information about collations, see Microsoft’s documentation.
Comments
only displays the collation descriptions that are supported by the operating system that
is installed on the client computer that is being used to create the database. That is to
say it displays those collations that match either the OEM or ANSI code pages that are
used by the client computer. If you have not selected the Validate Code Page option,
the Collation tab displays all the available collations.
If you select Windows Collation, you should choose a collation that matches your
geographic location/language needs as closely as possible. The binary, casesensitive
and accent-sensitive properties of the collation that you select can be
modified. Selecting Binary will clear both the Case-sensitive and Accent-sensitive
properties. Selecting either the Case-sensitive or Accent-sensitive properties will
clear the Binary property. Use the AssistButton h to see the Windows collation
descriptions that are available.
When you select SQL Collation, the binary, case-sensitive and accent-sensitive
properties are inactive because they are included in the collation description and you
should choose a collation description that matches your code page and the required
binary/dictionary and case-/accent-sensitive characteristics. Use the AssistButton h to
see the SQL collation descriptions that are available.
Each new database you create can use a different collation. After the database has
been created, you can change the collation that it uses by clicking File, Database,
Alter. For more information about altering the database and changing the collation,
The Collation tab also contains an option called Validate Code Page. This option is
selected by default. If this option is selected, every time a client connects to the
database the OEM or ANSI code page that is used by the client computer is checked
to make sure that it is compatible with the code page used by the database. If this
option is not selected, the code page that is used by the client computers is not
validated.
You can disable this option if you are sure that every character is converted correctly
between all the clients and the database. Disabling this setting allows clients that are
using different regional settings (code pages) to use the same database even though
some characters entered by one client may not be interpreted correctly by another
client or by the server.
Other problems that can be caused by not validating the code page are:
· The sorting of textual data is governed by the database server and this means that
the data may not be sorted according to the rules specified on the "incompatible"
client computers. This problem will be more acute if there is some C/AL code that
only works correctly when a particular sort order is selected.
· If you are accessing SQL Server with external tools, these tools may not be able to
read the data that has been entered by the "incompatible" clients correctly.
We therefore recommend that you use the default setting and validate code pages
because this will avoid all these problems.
For more information about collations, see Microsoft’s documentation.
Regards
Dynamics NAV Enthusiast
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!