on 08-26-2008 3:45 PM
Hi
We are upgrading our MS SQL 2000 32 Bit instance to MS SQL2005 64 bit running on Windows server 2003 64 bit, this is running ECC 5.
I have just successfully updated the DEV system with these steps :
Preserved the jobs/users by outputting to script
Detatched the DB
Uninstalled SQL2000 32 bit
Installed SQL 2005 64 bit
Attached the DB
Ran SAP MS SQL Tools using the option 'Upgrade to MSSQL 2005 or higher'
I did this on our DEV system 2 weeks ago without error and SAP/SQL have been running fine without errors, but then I re-read OSS Note 799058 before doing the QA SQL upgrade and it seems to say you should use the 'Database copy' option ? but this is the same the DB I am re-attaching, there is no SID rename and I am upgrading from sql 2000 32 bit to sql 2005 64 bit, so there is no straight upgrade path ?
Does anyone know the difference in the SQLTOOLs options 'Upgrade to MSSQL 2005 or higher' and 'Database copy' ? we have had no problems since upgrading 2 weeks ago, I am just concerned we might hit an issue and what is the option to use doing this on QA as we need a consistant environment.
Thanks.
You may be still running in compatibility mode if you simply attached the database.
The SQL 2005 instance will house SQL 2000 databases if you simply attach them.
If you right-click on the database inside the management tools and go to properties, you will see the database is version 8. It should be 9 (2005).
Please check the SAP migration notes to verify that you go through the proper steps to migrate to 2005 from 2000.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
SAP have responded to a message I raised, stating there is very little difference between the DB copy and DB Upgrade in the MS SQL tools :
'In the case of system copy, the logins are created new.
In the case of upgrade, these logins are already exists in the SQL release upgraded from. '
So it looks like the only difference is with the users, that I had preserved and recreated anyway.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You may want to convert the code page to BIN2 before you upgrade to SQL 2005. You can run non-unicode on BIN2 perfectly fine, and it makes future unicode coversion (if planned) easier.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.