Deployment concerns

vbboyd · November 12th, 2013, 10:29 AM

So if you are using the following connection string in your web.config file for your test environment. Does this connection string need to change for the production server?

Code:

 <connectionStrings>
    <add name="WebShop" connectionString="server=(local)\SqlExpress;AttachDbFileName=|DataDirectory|CandyStore.mdf;Integrated Security=true;User Instance=true"/>
  </connectionStrings>

Imar · November 12th, 2013, 12:27 PM

It depends.

If your host machine runs SQL Server Express, then no. Otherwise: yes.

Most hosts don't support SQL Express so it's likely you need to update your connection string to match their instance of SQL Server.

Imar

vbboyd · November 12th, 2013, 02:00 PM

When I put that database under the SQL OEM and attach it to SQL server I get the following error message:

Code:

The database 'C:\XXX\APP_DATA\CandyStore.MDF' cannot be opened because it is version 706. This server supports version 655 and earlier. A downgrade path is not supported.
Cannot open user default database. Login failed.
Login failed for user 'Owner-PC\MrJones'.

The current instance of Sql Server is 2008R2.
What can you do to fix this problem. I will look online and see if I can get hits back on the error message.

I have both 2008 and 2012 SQL Server on my PC box. Could you reattach to the SQL Server OEM tool for 2008 and get different results?

Imar · November 12th, 2013, 06:20 PM

Google should give you many results on this error, all saying that you can't attach a 2012 database to a 2008 / 2008R2 instance.

Attach your database to a 2012 instance, or recreate the database under 2008 / 2008R2.

Cheers,

Imar

vbboyd · November 12th, 2013, 06:26 PM

Quote:

Originally Posted by Imar

Google should give you many results on this error, all saying that you can't attach a 2012 database to a 2008 / 2008R2 instance.

Attach your database to a 2012 instance, or recreate the database under 2008 / 2008R2.

Cheers,

Imar

Attach your database to a 2012 instance, or recreate the database under 2008 / 2008R2.

Yes I can do this using DTS. I can take the old data from the old database and DTS it over to the new database and off we go. My only concern that when using DTS that you won't get the full Database functionality with it like all of the triggers, cursors, functions and stored procedures. I am not sure that would port over as well using the DTS utility of SQL Server 2012

Imar · November 12th, 2013, 06:29 PM

The database publishing wizard in 2012 can do that.

Also, DTS can do what you mention; you just need to make use of more of the advanced DTS features.

You can also script the current database as SQL 2008 compliant, recreate it against 2008 and then use DTS to copy over the data.

Imar

vbboyd · November 12th, 2013, 06:35 PM

Quote:

Originally Posted by Imar

The database publishing wizard in 2012 can do that.

Also, DTS can do what you mention; you just need to make use of more of the advanced DTS features.

You can also script the current database as SQL 2008 compliant, recreate it against 2008 and then use DTS to copy over the data.

Imar

SQL Server has a 2012 publishing Wizard? I will have to check it out. Sorry I meant to say SSIS, I have used DTS so much in the past on the job that I have it on the brain and can't get it out. My bad.