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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installed With Two Different DB Connections in web.configInstalled With Two Different DB Connections in web.config
Previous
 
Next
New Post
4/8/2010 2:25 AM
 

Long story short: The site got moved to another server. Backed up from old database server (external to the web server) and moved the site to a new server with SQLExpress running locally. Got it up and running seemingly just fine. Until now, several months later, when I add a new FAQ, I got a foreign key constraint error. Problem is, it was on the wrong database. Turns out I did this.

 

<connectionStrings>
<!-- Connection String for SQL Server 2005 Express -->
  <add name="SiteSqlServer" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=False;Database=XYZ;" providerName="System.Data.SqlClient" />
<!-- Connection String for SQL Server 2000/2005
  <add name="SiteSqlServer" connectionString="Server=123.456.789.0,1433;Database=ABC;uid=NA;pwd=NA;" providerName="System.Data.SqlClient" />
-->
</connectionStrings>
 

 

<appSettings>
<!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules
  <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=False;Database=XYZ;" />
-->
<!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules-->
<add key="SiteSqlServer" value="Server=123.456.789.0,1433;Database=ABC;uid=NA;pwd=NA;" providerName="System.Data.SqlClien;" />
 

...

In other words I had the site running partly on one database and partly on the other. What things should I be on the lookout for? Is there a list somewhere of which parts of the system use the which connection? 

 
New Post
4/8/2010 4:25 AM
 
some of the modules may still save their content using the legacy (lower) connection string. I suggest making both the same and look at your site for missing records. Another chance is comparing the number of records in both databases. Depending on the number of records affected, you may transfer data manually or by SQL.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installed With Two Different DB Connections in web.configInstalled With Two Different DB Connections in web.config


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