Is setting the COLLATION within SQL Server 2019 installer still an important step, as it was back in E9 days? @JWard
Many Thanks
Mark
Collation should be
SQL_Latin1_General_CP1_CI_AS
According to Epicor / EpiCare
https://epiccare.epicor.com/epiccare?id=epiccare_kb_article&sys_id=6881f680db2b6a04b3227e09af9619ad
Excellent, thanks Jose. That article confirms my findings, that it talks about E9 but not E10 and greater. I’ll set it to that recommended one.
See you in May!
Looks like I need to fix my notifications!!
What I was taught all those years ago (6 now 
) is that E9-10 Upgrades must use the collation as per Jose’s link and comment. If a (new) customer started on E10/Kinetic then I was told it doesn’t matter… now that’s with my UK hat on of course, and we do have customers around the world on collations that match their regions.
For new installs today we still set it to SQL_Latin1_General_CP1_CI_AS in the UK.
1 Like
@JWard I remember a presentation you gave in the UK, probably EUG event from memory.
Also think you may have setup my first Epicor environment back in 2010 ish kind of time… 
In my mind the _CI_AS bit is still important
EUG 2017 and 2018 was most certainly me!
2010… no chance, was still at University then 