MS-SQL Server Collation "SQL_Latin1_General_CP1254_CS_AS"

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
7 years ago
If you are using this MS-SQL Server Collation "SQL_Latin1_General_CP1254_CS_AS" if you receive an error!
This Collation does not accept the spelling of some tables and parameters are case sensitive.
Here is a list that needs to be fixed.
After you have corrected this list, you can use this collection.

NewsletterSubscription
Incorrect
CREATE NONCLUSTERED INDEX [IX_NewsletterSubscription_Email_StoreId] ON [NewsletterSubscription] ([Email] ASC, [StoreId] ASC)
Correct
CREATE NONCLUSTERED INDEX [IX_NewsLetterSubscription_Email_StoreId] ON [NewsLetterSubscription] ([Email] ASC, [StoreId] ASC)

ShowOnHomepage

Incorrect
CREATE NONCLUSTERED INDEX [IX_Product_ShowOnHomepage] ON [Product] ([ShowOnHomepage] ASC)
Correct
CREATE NONCLUSTERED INDEX [IX_Product_ShowOnHomePage] ON [Product] ([ShowOnHomePage] ASC)

Incorrect
LanguageID
[dbo].[LanguagePackImport]
Correct
LanguageId
[dbo].[LanguagePackImport]

Incorrect
CustomerID
[dbo].[DeleteGuests]
Correct
CustomerId
[dbo].[DeleteGuests]

Incorrect
EntityID
[dbo].[DeleteGuests]
Correct
EntityId
[dbo].[DeleteGuests]
7 years ago
Thanks a lot! I've just applied the changes (commit)

But please note that anyway you should not use case sensitive collations. It can cause some issues. For example, when searching customers by email (we make this validation during registration). Otherwise, customers will be able to register with the same emails. I've create a separate work item for this task
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.