Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

About

News Press Releases News Coverage Press KitCareersContact DNN

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsStoreStoreSQL Execution failureSQL Execution failure
Previous
 
Next
New Post
11/13/2007 12:19 PM
 
Jan Durian


Joined: 6/5/2004
Posts: 181

Follow-up ...

The error number from Query Analyzer is: Server: Msg 446, Level 16, State 9, Procedure ...

The best way to deal with collation conflicts is not to have them, but we often have no such choice. This problem can be solved generally in two ways:

  1. Every time you use a temporary table (or other such object), create the temporary table with the desired collation or add the desired cast (collate clause) when necessary.
  2. Have a different SQL Server instance for each collation.

Neither option is ideal, but better solution seems to be to have a different SQL Server instance for each collation. This is of course not possible in shared environments, therefore I suggest for this particular case following general workaround.

The only during install failed stored procedure creation is the procedure Store_Cart_PurgeCarts. It begins on line 600 in 01.00.00.SqlDataProvider file. You can insert collate clause for CartID column in OldCarts table declaration on line 606. The result looks like this:

DECLARE @OldCarts table (CartID nvarchar(50) collate database_default)

Collate database_default clause causes the collate clause to inherit the collation of the current database.

I tested this correction successfully for two scenarios:

  1. System database collation SQL_Latin1_General_CP1_CI_AS and user database collation Slovak_CI_AI.
  2. System database collation Slovak_CI_AI and user database collation Slovak_CI_AI. It’s strange, but in this scenario I am getting the same error as for the first one. May be it imply some sort of code page problem because SQL Server can support only code pages (and relevant collations) that are supported by the underlying operating system.

Gilles, one more question: Column CartID in table Store_Cart is defined as nvarchar type. Why? It’s the primary key and with integer type (for example :) we have no collation problem.

Jan
 
New Post
11/14/2007 8:05 AM
 
Gilles Le Pigocher


Joined: 10/11/2003
Posts: 1966

Hi Jan,

Thank you very much for your work on this problem! That will surely help other users.

I do not know why the CartId use the nvarchar datatype. I'm not the original developer of the Store module. I work on this project and his ancestor (WWStore) since 10 months surroundings. I already corrected many bugs and made many improvements. But I have still much work to make on this project!

I will look inside the old versions (01.00.00 and 01.00.01) why they use nvarchar. If that not created problem for the update, I would make the modification in a forthcoming version.

Gilles

We (team members) are Humans offering their knowledge, their work and their spare time FOR FREE to benefit the community. It would be so particularly appreciated that your messages begin with "Hello" and end with "Thank you" or any other form of politeness. Ask yourself what your reaction would be, if you were approached by me (a total stranger) on the street to ask you something without saying "Hello" nor "Thank you"? After several years of services dedicated to the community, I begin to be tired to read requests without any form of politeness.
 
 Page 2 of 2
Previous12 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsStoreStoreSQL Execution failureSQL Execution failure


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out