Products

Solutions

Resources

Partners

Community

About

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 ...Need help BIG timeNeed help BIG time
Previous
 
Next
New Post
7/15/2009 2:08 PM
 

Alright I have no idea how I managed to do this but here's my current situation. I've been experimenting with dotnetnuke for about 2 months now. I have a working site and have a bunch of data on it. So today I was experimenting with backing up and restoring the site to a completely new server. I was attempting to modify the portalaliases table when I noticed that I don't have one. Not only do I not have one but more to the fact that the database is completely empty, there's nothing in it whatsoever. So I looked at my web.config file and noticed I'd misspelled the server name in the SQL connections string. There are an mdf and an ldf in the virtual directory and I assume those are where everything is, my question is how could this have possibly worked? If the SQL connection string was pointing to a completely different server (one that actually is no longer on the network at all) how have I gotten this far? There are 2 completely different MDF and LDF files, one having the proper database name the others being called database.mdf and database.ldf. More importantly how do I fix this.

 
New Post
7/15/2009 2:43 PM
 

I assume, you are looking at the wrong connection string, make sure, to refer not to the commented one (in <!-- .... -->)

Most likely you are using /app_data/database.mdf. check the size and make sure to use same connection string on the target server.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/15/2009 3:59 PM
 

So it's 100% normal for the database I created to be completely empty and all the data to be in this application created database? Seems kind of pointless to require you to create a database if it's not going to be used doesn't it?

 
New Post
7/16/2009 5:28 AM
 

you only need to create a database in SQL Server, if you want to use it - and there is a big advantage, because you can open it with Management Studio.

If you decide to use the file based access (select to use "Express" database in installation wizard), database.mdf is used, if you select SQL Server (even for Express being installed), you use a previously created database (what I prefer).


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Need help BIG timeNeed help BIG time


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