Technical Upgrade from 4.00 to 4.03 (SQL)

ta5

Hi
I know this has been discussed in some kind before, but I would like to have some pros and cons for a discussion:

As far as I understand there are 2 options to do a technical upgrade. Its with SQL-Server 2000.

1) Create new Datatabase and restore a backup from the 4.00 DB
2) Just install the new clients and do the conversion on the production DB upon first connection (of course taken a backup first)

What are the pros and cons for these 2 options? By the way: Would the answers be the same if native database were used? Many thanks in advance.

Thomas

nunomaia

I don't see much difference in upgrading in both ways. If you upgrade from Native you must first convert dates.

ta5

Thanks nuno.
Anybody else with a comment? I'm looking for a kind of "best practice".

Thomas

David_Singleton

ta5 wrote:

Hi
I know this has been discussed in some kind before, but I would like to have some pros and cons for a discussion:

As far as I understand there are 2 options to do a technical upgrade. Its with SQL-Server 2000.

1) Create new Datatabase and restore a backup from the 4.00 DB
2) Just install the new clients and do the conversion on the production DB upon first connection (of course taken a backup first)

What are the pros and cons for these 2 options? By the way: Would the answers be the same if native database were used? Many thanks in advance.

Thomas

For a major upgrade I would do 1/, but for a routine Service pack update, or from a version to another that I know works OK, I would do 2. But always do a DB test afterwards. If you don't have enough experience to know which versions are risky, then best not take that risk, so...

If you are asking BEST PRACTICES, then I would always recommend the backup restore path, (1) since its the proper way.

nunomaia

Just one comment.

During a very few upgrade from 3.70 to 4.0 SP3, conversion had hanged during upgrade. In those migrations I had take the second option.

That I also recommend following David advice and always doing first in a test DB to ensure everything is done properly.