Hello.

I plan on building an ASP.NET 2.0 web application using Visual Web Developer 2005 Express.  Currently my only mode of publishing said site is with GoDaddy.

I played around a little bit today and I can see I'm going to have problems.  I'm not sure what exactly I should do about my database.  I don't think I can keep it in my App_Data folder (I don't think this is a good idea anyway).  I'm also not sure how GoDaddy does SQL.  I know I can create 2 virtual SQL databases.  But how do I get the database on GoDaddy and the one on my computer to "sync"?

I guess I'm just really not sure what the best course of action would be.  Any help would be appreciated.  :)

Well,firstly you need to know what Godaddy supports.We provide our customers with a SQL tool suite which has an easy to use  'Attach DB' functionality (attaches the mdf to our SQL Server).I recommend you to first find out out what they support.

Let me know if you need more help. 

I know it supports SQL 2000, but I have to create the database using their control panel.

The problem is is that I can't link to it from my work PC because GoDaddy doesn't allow remote linking.  How then do I develop my application if Web Developer is constantly spitting out errors stating it can't find the database?
 

GoDaddy uses SQL Server. Because they don't allow remote connections, there's a bit of work involved in keeping your two databases in sync. But it can be done. You basically have two options (there are more complicated ones that require coding):

Option 1: Use GoDaddy's point-and-click tools to recreate your tables (fine for a small number of tables, tiresome for a lot)

Option 2: Generate a SQL script from your local database (one that has lots of "create table" statements) using one of several tools available (not Visual Web Developer itself). Copy-and-paste the contents in to the GoDaddy query tool

If you're using SQL Express as your local database, then be aware that the database connection in your live web.config file will be different to your local environment. I've put together a document on what needs to change for shared hosting using SQL Server with some hints at where to find the information you'll need.

 http://www.salmontraining.com/SqlExpressZone/Articles/why_the_development_config_file_wont_work_on_live_shared_hosting_with_sql_server.aspx

Margaret

My previous post of 13th April was correct at time of writing in saying that Go Daddy disallows all remote connections to SQL Server on the shared hosting plan.

As of August 2007, they are now allowing connection with the Database Publishing Wizard (free Microsoft download) to deploy databases (schema and data).