Developer forum

You do get some warnings on index sizes and updates of related tables. Just say yes to that.

Hi,

The problem with the collations is not only applied to the EcomProducts. This will apply to almost any search we have on the website. We have been using "SQL_Latin1_General_CP1_CI_AI" collation in our databases for quite a while because in Portuguese  we use a lot of accents, but after a while, when updating to newer Dynamicweb versions the problems started to show and some scripts would not run like the creation of the EcomRMA tablesand others. Dynamicweb Helpdesk has provided me with a collation fixer tool to solve some issues, however, eventually it was messing to much with the database so we had to change the collation again into "SQL_Latin1_General_CP1_CI_AS" so that the Dynamicweb updates would run without a problem.

It seems a little bit "messy" changing the colation for only two columns and while that solves the problem for products it doesn't solve for Pages and Paragrafs. It would be great if it was possible to have Dynamicweb update scripts independent from the collation in use.

BR Diogo Brito

You have a valid point. Dw should have better support for accent insensitive.

Nice feature would be the have this configured on website level or the complete installation.

A quickwin could that we can agree that de dw default collation goes to SQL_Latin1_General_CP1_CI_AI (for defaultemptydata and solutionset db)

Dw can test and fix issues and say the next version is AI compatible.

I know it can be pain if temp tables are created in sql server because these are by default in the collation of the sql server setting. It should all be fixable :)

Hi Diogo & Remi

There is a difference between setting the AI collation for the entire database and selected fields.

Will look into if we should release an AI version.

BR Nicolai

Hello Nicolai,

Did this situation suffred any development?

BR, Diogo Brito

No it did not.