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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Issue migrating to a new databaseIssue migrating to a new database
Previous
 
Next
New Post
5/5/2011 2:08 PM
 
I am in the process of migrating my DNN app to a new database on a different server.  The current database is a SQL Express instance mounted on a SQL Server v10.5 database.  The new database is not SQL express, it's a SQL Server database on version 10.0.

I was able to copy the database to the new SQL Server instance and have updated the Web.config file to point to it.  Now when I try to access my website, I get the DotNetNuke Installation Wizard.

I assume I shouldn't go through the install wizard, as I'm worried it might overwrite my existing application.  I also noticed there's a key in Web.config called UseInstallWizard.  Maybe I should set that to false.

Any suggestions are appreciated.

Cheers,
Matt
 
New Post
5/5/2011 9:06 PM
 
AFAIK you cannot mount a 10.5 database on SQL Server V10.0, unless it has been created originally by a prior version. You need to attach the database to the SQL server and grant DbOwner permission to the user, used to access the database (which needs to be configured properly in BOTH uncommented SQL connection strings in your web.config file).

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
5/13/2011 10:13 AM
 
I think you're right.  After a fair amount of research, this is what I think we'll need to do.

Script the creation of all of the database objects and run the create script in the new database.
Use the SQL Server import/export data function to populate the tables in the new environment.

One sticking point that I'm aware of is that while importing data, we're going to run into foreign key constraints that prevent the inserts.  Maybe we'll end up deleting all FKs on the database and recreating after the import.

-Matt
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Issue migrating to a new databaseIssue migrating to a new database


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