Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Upgrade from v5.5 to v6.1

Status
Not open for further replies.

vbdbcoder

Programmer
Nov 23, 2006
247
US
We are evaluating an upgrade for a client from v5.5 to v6.1. The Accpac database has a size of 45 gig with a log file of 43 gig. And the SQL database is in SQL 2000.

Struggling on if we need to upgrade the database server from SQL2000 to SQL 2008R2 first, and then do the upgrade of Accpac. If upgrade only SQL server 2000 to SQL server 2000R2, would database detach and then database attach work?
 
Set the database Recovery Model to SIMPLE for crying out loud!!!!! Then shrink the database.
You have to upgrade SQL first, 6.1 WILL NOT run with SQL 2000 - so you have no option there.
After installing SQL 2008 you must edit the database and set the Compatibility Level to 100 for SQL 2008 (I think???). Detach/attach will not do anything else besides detach/attach and waste some time.
 
A log file of 43 GB sounds like you might have never backed up the log file. Or you're rebuilding indexes in the middle of the day.

In general, if you have a problem with your Accpac database you're going to restore the whole thing to "yesterday's backup". If that's the case then do as Ettienne said and change the recovery model to simple. That will keep your log small. If you have a good DBA on staff then by all means back up your log every two to four hours so you can avoid losing 4-6 hours of transaction time (while you wait for a 45 GB database to be rolled back ;-) ).
 
I have not found one DBA that understands how SQL logs work, sad really....
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top