‎2008 Oct 29 1:43 PM
Hello
We are using ECC 5.0 on Windows 32-bit and SQL Server 2000.
We want to migrate to platform Windows 64 bit. We know the procedure described on note 960769-Windows:Migration from 32-bit to 64-bit.
We know we can use R3load to do export/import, and we are going to install SQL server 2005 in target server.
So, with this procedure we will be in ECC 5.0 , Windows 64-bit and SQL server 2005, but the main question is.. how Unicode conversion play here?
Can we take advantadge of this migration performing Unicode Conversion too? How? Is Unicode Conversion obligatory here?
u2026
Thanks and regards
Javier
‎2008 Oct 30 10:52 AM
Hi Javier,
first of all, your upgrade to SQL Server 2005 64bit could be done without Migration. You just have to upgrade your database and you're done.
If you would like to migrate to Unicode you could do this by migrating from 32bit to 64bit with R3load. Actually when you want to migrate to Unicode, the you should do it with a small and simple system. Simple means here with single code page or few code pages. If you plan to install new languages which would introduce new code pages, then a Unicode migration should be done before you add the language. Small means, when your system grow significantly, then you should migrate soon. When you started an archiving project, then you probably better wait till this project lead to a smaller system. In other words. The less code pages you have and the smaller your system is, the better it is for your Migration. Downtime will be smaller and the project complexity will be less too.
Best regards
Ralph Ganszky