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 ...DNN cloneDNN clone
New Post
6/17/2013 2:39 PM

Our web server was just cloned so that we can have a staging environment. What steps do I need to take so that the database on the production server is not written to?

Here is what I am thinking - modify the connection strings in web.config on the clone so it references Database_test instead of Database and then rename Database to Database_test. Is this all I need to do to be 100% safe from overwriting the live server? I am particularly nervous because the 1st thing I intend to do with the staging environment is upgrade DNN CE 5.6.2 to the current version 7.

Your feedback is welcome and very much appreciated.

New Post
6/19/2013 5:34 AM

You can follow below mentioned steps


  1. Add New HTTP Alias for your site to access from production server. To do so you need to click on “Site Settings” link under ‘Admin’ tab and click on “Add New HTTP Alias” link. Give a new site URL (As you wish to access the site with name). There is one rule which need to be followed when you set the alias for your production site, do not use the HTTP before your alias name. For example if you want to access your site with name http://www.myfirstsite.com then you must add the alias as www.myfirstsite.com . The other way to set your site URL/ alias is to set it at database. You can set it in “PortalAlias” table.
  2. Take a back up of development server Database.
  3. Move your physical folder (site folder) from development server to production server. Create a virtual directory through IIS and set the web site properties as you have set at your development server. 
  4. Create a new Database at production server and restore the back-up database (The one you take from your development server). 
  5. Open the web.config file of production server and set the “connectionStrings” as below:

    <!-- Connection String for SQL Server 2005 Express -->
    <add name="SiteSqlServer" connectionString="Data Source=Production server ;Initial Catalog=Database name;User ID=UserID;Password=Password" providerName="System.Data.SqlClient" />
    <!-- Connection String for SQL Server 2000/2005
      providerName="System.Data.SqlClient" />

6. Reset the IIS once.

7. Now you can access your site through the URL you gave above.



New Post
6/21/2013 9:23 AM
Perfect. I am all set up now. Thank you.
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN cloneDNN clone

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.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  

Copyright 2018 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out