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

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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...Migrate from SQL2000 to SQL2005 - something to keep in mind ?Migrate from SQL2000 to SQL2005 - something to keep in mind ?
Previous
 
Next
New Post
11/29/2007 4:23 AM
 
Sebastian Leupold


Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

www.dnnwerk.de
Joined: 3/8/2004
Posts: 46212

SQL 2005 can use all collations from SQL 2000. Server collation is overridden by the database collation.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
11/29/2007 4:24 AM
 
Sebastian Leupold


Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

www.dnnwerk.de
Joined: 3/8/2004
Posts: 46212

ROBAX wrote

 digmike wrote

 

Once you are done restoring like Sebastian said, you may want to go to the DB options and change your combatibility  level to SQL 2005.  For a full list of differences between the levels, look in the SQL 2005 BOL.

Mike, can you elaborate a little on this point for a db noob. Where are these db options? Is this a DNN setting?

as long as DNN supports SQL2000 there is no need to increase comatibility level.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
11/29/2007 6:07 AM
 
ROB AX

Joined: 9/3/2004
Posts: 2185

Sebastian Leupold wrote

as long as DNN supports SQL2000 there is no need to increase comatibility level.

cool thanks for the info
 
New Post
11/29/2007 12:37 PM
 
Mike Santoro


Joined: 10/25/2006
Posts: 371

Hi Rob,

In SQL Management Studio, right click on your db and select Properties.  Then choose options. Look here for more info.  It's basically different features and syntax in SQL that are allowed or not allowed based on your compatibility level.  It should be fine to keep compatibility at SQL2000, but I always set mine to 2005.  Since I'm using SQL Server 2005, why not set the compatibility to 2005?  I notice more and more modules requiring SQL2005, I don't know why they require it.  Maybe because they just don't want to test on 2000, or maybe they are using 2005 specific features and syntax that just may require 2005 compatibility level. 

Thanks,

Mike

dignuke.com DotNetNuke Modules
DotNetNuke Modules
 
New Post
11/29/2007 7:32 PM
 
Dan Zhang

Joined: 11/20/2005
Posts: 34

I know sql2005 can use sql2000 collation,but if you create TEMP table in stored procedure and use the one of the columns in TEMP table compare with DNN existing table, then will have the collation problem.

 

Dan
 
 Page 2 of 3
Previous123Next 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Migrate from SQL2000 to SQL2005 - something to keep in mind ?Migrate from SQL2000 to SQL2005 - something to keep in mind ?


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