concerned about SQL server version confusion

Hi...I don't want to sound too pessimistic but I'm a little concerned I have on 2 occasions had to purchase SQL accounts simply because I was so confused as to how to connect to a database that I inadvertently lost my database.

Apparently this also happens to other developers...

I'm currently using VWD2008/SQL2008 but after the bad experience I've had with VWD2008/SQL2008 I'm considering reverting back to VWD2005/SQL2005. Although I had a few problems with the proverbial conncetionstring problem to database and attach mdf panel tools loading data to SQL2005 server I was finally was able to connect to my SQL 2005 server account. Had no problem with querying database for 6 months till I was given the advise to upgrade to VWD 2008 & SQL2008.

Now I don't know what to do.

I have lost all data in my present account my data driven section of site is down no roles and membership and can't query the database.
I've read the respective KBs and seen the videos and still find it difficult to migrate from VWD2005/SQL2005 to VWD2008/SQL2008 to achieve a finished product, query to a database that needs to be built. And confidence that manipulating data won't be lost because some procedural regime was slightly flawed in execution causing confusion.
I don't know if I should continue to develop under VWD2008 and load to a SQLserver 2005, I don't think this is possible or is it possible without problems.

I would need to know some advice since I have to inform DASP my intentions on creating a whole new SQL ??? server account.

For example: What happens to my VWD 2005 App_Data folder and App_Code folders on computer's drive. Would I need to pull these under VWD2008 and edit them?
Then load them to my remote site root. What happens to old ASPNETDB.mdf does this need to upload to my remote site?

There has to be a more fluid procedure in migrating and manipulating database than what is currently being offered.

There seems to be no phone support which I would need if I had paying customers who depend on their data being available. Where do DASP customer developers get emergency help if a problem were to arise?

I wouldn't mind paying for this phone assistance.

 

Visual Studio 2008 is actually intended to work with SQL 2005. When you add a new MDF database file to the App_Data folder, VS2008 will use SQL 2005 Express. So at least on your computer, I recommend running SQL Express 2005. It is ok for your DiscountASP SQL database to be either 2005 or 2008. You will be able to attach your local SQL Express 2005 database MDF file to your DiscountASP SQL 2005 or 2008 database.

Your code in the App_Code folder should safe if you open/convert a Visual Studio 2005 project with Visual Studio 2008.