Hello:

I've installed DNN4.x without issue using VS 2005 and SQL 2005 (I'm not usring SQLExpress).  I've FTP'd the website to my ISP.  In SQL 2000 I would use Enterprise Manager and the "Export Wizard" to copy my database to my remote site.

In MS SQL 2005 there isn't such a feature.  Has anyone been able to successfully deploy an MS SQL 2005 database, DNN or otherwise, to their ISP?  Any help is very appreciated!

John

Hello: The App_Data directory is not a required directory, i.e. your DNN database can reside in your MSSQL Data directory.  Since I created the empty database from SSMS for my DNN site, this is where the database resides.  The web.config file and portal alias value where changed.

I am sure the issue is with the database because it works perfectly fine locally and my local schema differs from that on the ISP/remote database.  I will also receive a message such as "cannot locate stored procedure xxx".  My ISP is CrystalTech and I've posted on their forum as well, but the advice pertained to "upgrading" and existing SQL 2000 database, or FTP'ing the database to them so that they can attach it.  I decided to FTP the database but when attached or when I received the support email that it was, the user account didn't work within their control center (nor did the application), or the database was empty, etc.  So I decided to give up on that approach.  I would prefer to control the exporting/uploading of my database myself anyway, so that I can change when needed and backup on a schedule.  I was able to do this easily in SQL 2000 using DTS, but cannot fine a comparable means in SQL 2005.

Thanks!
John

I appreciate your attempt in giving me advice, but it sounds like you are having the same or similar problems(?)  You can create a backup such as you noted and your ISP can restore it, you just need to tell them your database to restore over, and in my case pay $5.

What I am looking for is a process to be able to move my database, which includes tables, views, and stored procs, and the relationships among these objects, so I'm not sure what you mean by the big question being which tables due to the obvious fact that it would be all of them, and all views, and all SPs.  The DTSWizard is a utility to make this feature backward compatable to SQL 2K, but I'm starting in SQL 2K5.

What needs to be done is to install SQL Servers Integration Service (SSIS) and run the SQL Server Business Intelligence Development Studio to create the 2K5 compatable package.  What I am running into appears to be permission issues, such as you would experience when trying to copy your database to the remote ISP.  Short of scripting the database, or having the ISP restore the database FTP'd to them, I haven't seen any reasonable way to manage the export of my SQL 2005 database, which I could do in SQL 2000.  Once I determine a way to do so, though, I will post the solution.

Thanks!
John