Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Cannot resolve the collation conflict between "Latin1_General_CI_AS"Cannot resolve the collation conflict between "Latin1_General_CI_AS"
Previous
 
Next
New Post
7/20/2010 1:29 PM
 
Dave Colbeck wrote:

Did you get a warning about having to drop the database and re-create it?

I've tested the dropping and re-creation through SQL Management Studio and all seems well, I just want to test more...

 you are talking about dropping the table and recreate not the database, right? this is ok, if the warning prevents execution you need to alter SSMS settings.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/20/2010 1:32 PM
 
Sebastian Leupold wrote:
Dave Colbeck wrote:

Did you get a warning about having to drop the database and re-create it?

I've tested the dropping and re-creation through SQL Management Studio and all seems well, I just want to test more...

 you are talking about dropping the table and recreate not the database, right? this is ok, if the warning prevents execution you need to alter SSMS settings.

 Yes,

It is just warning about dropping the table and re-creating the table.  I had to change the options in SSMS to allow it to happen.  All of the data seems to be there still, so I am guessing that the process scripts out even the data.


-----
Cheers
Dave
 
New Post
7/20/2010 4:54 PM
 
that sounds fine :)

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/22/2010 3:00 AM
 
Hi,

i didn't have to drop my table. I just used the query to see which columnnames had an incorrect collation.
Then i used management studio to adjust the collation of these columnnames to my default database collation.

Hopes this helps you. Sorry that i didn't replied earlier.
We don't work on july 21st.

Greets,
Stephany
 
New Post
8/5/2010 2:44 AM
 
I finally got time to do this. Almost 5 hours later, I have a fixed site. Thanks everyone for their help and patience. Cheers

-----
Cheers
Dave
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Cannot resolve the collation conflict between "Latin1_General_CI_AS"Cannot resolve the collation conflict between "Latin1_General_CI_AS"


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