Collation

Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

Post here for help with installation of mojoPortal pre-compiled release packages

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.

You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

This thread is closed to new posts. You must sign in to post in the forums.
6/15/2011 4:47:05 PM
Gravatar
Total Posts 55
mojoPortal Community Expert
Arvixe Web Hosting / mojoPortal Community Liaison Looking for quality mojoPortal hosting? Try Arvixe Check out the MojoPortal Blogs at Arvixe

Collation

Hi,

I've got a question about collation.

short question:
Is there any argument against setting the collation for local databases to be the same as my hosted databases and is there a way to set the default?

using latest MojoPortal ASP.NET v4 windows MS SQL 2008r2 Express

longer version of the question:

Collation is something I was blissfully unaware even existed until recently. I became aware of it when I started getting collation conflicts. In MojoPortal I get one if I go to the member list - it occurs if my local database has one collation and remote has another. The error I get is: Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.

To change the collation of a local database - now that I have SQL Server Management Studio installed & know how to get to that option - takes maybe a minute or two, although its an annoying waste of time. Getting a hosting provider to do it can take a few days. I vaguely recall reading there's not much impact in choosing one collation over another, so I plump for changing mine.

I'm treating it as if its really not important.
Anyone know if this is likely to cause me any problem in future?

And if anyone knows how I can set my default collation that would be really handy.

I've done a bit of digging on collation, and will do some more, but so far have not happened across a good resource for it.

You must sign in to post in the forums. This thread is closed to new posts.