Hello;
You could use different databases in a scenario like:
1. Existing database
2. Write new modules to point to a 2nd database

In this case you would need to create and manage the data pipeline yourself

We do not suggest switching the whole application between databases as this involves maintaining machine keys and hashes for your existing users.

---

Ken Grierson
DotNetNuke Corporation
Test Lead

you don't need a new database to migrate the underlying hardware. just backup the database and restore on new sql server (same version or newer) and transfer all files to a new website folder, you may configure identically like the old one.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN