Page 1 of 1

Migration SQL 2000 to SQL 2008 R2 for AC 7.0

Posted: Tue Jan 11, 2011 5:01 am
by Pawan
I would like to migration from DB SQL 2000 to SQL 2008 R2.
My current ablecommerce details as follows:
PLATFORM: ASP.NET
VERSION: 7.0 BUILD: 9381
SQL: 2000
I already tried new installation (http://help.ablecommerce.com/installati ... sp.net.htm), but I could not find SQL 2008 in Database type.

I really appreciate any help you can provide. Thank you.

Re: Migration SQL 2000 to SQL 2008 R2 for AC 7.0

Posted: Tue Jan 11, 2011 12:38 pm
by mikek
If you need to migrate an existing AC 7.0 site database from SQL 2000 to 2008 R2 you just need to create full database backup from the existing MSSQL 2000 server and then restore the backup file
under a new MSSQL 2008 R2 instance. Make sure you have a valid MSSQL 2008R2 DB login assigned to the database after the restore is done.

Another change you may have to make is changing the DB connection string in App_Data\database.config file. No licensing or other app. changes is required.

Re: Migration SQL 2000 to SQL 2008 R2 for AC 7.0

Posted: Wed Jan 12, 2011 12:16 am
by Pawan
Thanks,

App_Data\Database.config file is Encrypted.
How can i change the DB connection string?

Re: Migration SQL 2000 to SQL 2008 R2 for AC 7.0

Posted: Wed Jan 12, 2011 3:45 pm
by mikek
If the file is encrypted the connection string must be changed from your site Admin section.

Re: Migration SQL 2000 to SQL 2008 R2 for AC 7.0

Posted: Thu Jan 13, 2011 7:36 am
by Pawan
Thanks a lot Michael,

I successfuly update my config file manually:
viewtopic.php?f=42&t=5747&p=61782&hilit ... ing#p61782

1) Make a backup copy of APP_DATA\database.config
2) Delete existing content.
3) Paste following it into database.config file.
<connectionStrings>
<add name="AbleCommerce" connectionString="Server=yourserver;
Database=yourDB;Uid=youruser;Pwd=yourPW;" ProviderName="System.Data.SqlClient" />
</connectionStrings>
4) Modify the connection string to have the correct new server, database name, username, and password information.
5) Save the updated database.config file.