Have you ever come across a collation problem in regards with Shoper, like \u2018Cannot resolve the Collation Conflict between \u201cSQL_Latin1_General_CP1_CI_AS\u201d and \u201cLatin1_General_CI_AI\u201d in the equal to operation\u2019?.<\/p>\n
If yes, then this article will help you understand the basics of Collation and how to resolve this issue permanently.<\/p>\n
A Collation is a set of rules that define how data types are sorted and arranged in regards with languages being used. For Example Latin1_General refers to – the Latin alphabet used by western European languages.<\/p>\n
For more details on Collation in SQL: http:\/\/www.sqlserverclub.com\/articles\/understanding-sql-server-collation-sequences.aspx<\/p>\n
This is mainly because the default collation of SQL (selected at the time of installation) being different from that of your Shoper database (and or its tables and fields). The required collation for Shoper is \u201cSQL_Latin1_General_CP1_CI_AS\u201d and should be set as Default Collation for SQL at the time of SQL Installation only. However if you try to change it later for Shoper Database, it will result in frequent occurrence of this Error every time a new patch is updated.<\/p>\n
Hence the only permanent solution to this issue is to reinstall the SQL with desired default collation. This is only possible if you\/ your client is not yet Live on the system and SQL contains no other databases. However if that is not the case then the only option you are left with is to Re-Install your Shoper Database from a Backup (with the help of Tally Support Team).<\/p>\n
For steps to install SQL Server: http:\/\/msdn.microsoft.com\/en-us\/library\/ms143722(v=sql.90).aspx<\/p>\n
Please consult your Tally Support executive before exercising any of the steps mentioned in this article as Solutions vary on a case basis.<\/p>\n","protected":false},"excerpt":{"rendered":"