First the question straight forward.  When I originally started playing with DotNetNuke, obviously I knew ZERO about much of anything :->.

can I somehow convert this .bak file I Have from SQL, to whatever is required in the app_data folder?

So, I set up SQLEXPRESS 2005, and created a database for DotNetNuke using Management Studio Express, which seemed the easiest at the time...I've later learned a much much easier way, which is to just use the database file in the app_data folder.  Anyhow comming from a newbie point of view you can understand the confusion, as it seems logical, that any data needs to show up in the sql management tool, and these files don't show up there :->

So...now I'm thinking how much easier it would be to move a website from one server to another, using this nifty, which does obviously still use SQL server...but then I wonder, what is the dis-advantage to using SQL EXPRESS using the app_data folder, as opposed to creating a database in the tool, that is somewhere burried in the SQL install folder....it just seems logical now, that one would prefer to use the app_data folder.

I can understand, if I want to use full blown sql, and want to maybe do some clusters or something, that maybe thats when to use this type install.

 

So...finally to the question(I can't help babbling :->).

I want to seperate two websites on the same DNN instance, to two seperate instances of DNN.   I now have two websites that I want to work on both, but don't want to screw one up when working with the other.

I've backed up the SQL database of the original instance, and the plan was to just duplicate the whole site(folders and database), restore my backed up database to a second SQL instance, called like Site2, and then point the web.config in the duplicate to this second database, and then delete all the portals out of the second install that are not related to this install....violoa....seperate..and it should work I think without much problem....use some host headers to keep em live on one server until the need to move it to another, which will be needed soon.

can I somehow convert my SQL .bak file I Have from SQL, to whatever is required in the app_data folder?(read below for full...word friendly, annoyingly confusing explanation of what I'm wanting to accomplish and what brings me to this point :->)

 

Thanks

Josh

 

---

Josh Martin

Josh,

You plan to separate the sites is perfect, but I STRONGLY recommend NOT using the .mdf file inside of the app_data folder, leave them as you haev them.

I have a recent blog post about this topic at http://www.mitchelsellers.com which explains WHY the dynamically attached .mdf files is a bad idea.

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services

Ok...Roadblock. 

My plan then, after we talked here, is to backup my live copy of my database. then "restore" that backed up database, to a new blank database.  Here is the new snag.

I have a backup file, no problem.  I create the blank database using Management Studio express, and try to "restore" to it from the backup files...and I get somethign to the effect of, you can't do that 'casue a database with that name already exisits...which it does.  I"m jsut trying to keep both instances on the same server for now, then after seperated spend the money on a truely seperate server, and easily move it.

 

So..how do I backup my existing live database called "DNNLive" in Management Studio Express, and then create a duplicate of it called say DNN_Live_Split, or NewDNNLive, or PostSplitDNN or whagever, on the exact same server?

Any good tutorials?  my google skills seem to be lacking today :->

 

---

Josh Martin