i've just met a customer who have implemented Dynamics AX database with an
SQl Server collation (SQL_Latin1_General_CP1_CI_AS).
I know that Microsoft recommand tu use a WIndows collation like
Latin1_General_CI_AS for example instead.
Any idea about the risks of using SQL collation ?
Greets,
Guillaume
The collations dictate how the characters are sorted/compared(CI/CS - case
sensitivity, AI/AS - accent sensitivity).
SQL_Latin1_General_CP1_CI_AS is in alignment with code page 1252. The
sorting rules for this collation(SQL Server collation) will be different
from Windows collation like Latin1_General_CI_AS. Ax recommends
Latin1_General_CI_AS.
As a followup, can I ask why the customer picked
SQL_Latin1_General_CP1_CI_AS. Is there a particular reason and what is the
scenario?
--
This posting is provided "AS IS" with no warranties, and confers no rights
"Guillaume" <Guil...@discussions.microsoft.com> wrote in message
news:1D0AC213-544A-4AA0...@microsoft.com...
I know what collation do and that Microsoft recommand Windows collation
rather than SQL collation for Dynamics AX.
But in a Dynamics AX point of view, i don't know if SQL Server collation
like SQL_Latin1_General_CP1_CI_AS could be a real problem for customer
implementation and what probel could occur ?
I know that SQL server collation could be a performance problem for database
with unicode and not unicode data in the same database, but all data in AX 4
is normally in Unicode, so it will may be not a problem.
Any idea of potential problems with AX and SQL server collation ?
I'm not sure that the customer know why SQL Server collation was chosen. ANd
before alerting the customer i would be necessary to have some arguments to
give him.
Greets,
--
This posting is provided "AS IS" with no warranties, and confers no rights
"Guillaume" <Guil...@discussions.microsoft.com> wrote in message
news:C13EF7F7-800D-4C26...@microsoft.com...