Version80 database compatibility level is not supported
-
I moved two databases from SQL 2000 to SQL 2005 using backup files.
I need to move a table from one of them to the other.
I setup a "Transfer SQL Server Objects Task" which failed with the following error:
Error: 0xC002F325 at Transfer SQL Server Objects Task, Transfer SQL Server Objects Task: Execution failed with the following error: "Version80 database compatibility level is not supported.".
Task failed: Transfer SQL Server Objects Task
Backward compatibility is installed (all options).
What goes wrong?
Are the two databases not "fully 2005" now?
Thank you,
Dinu
-
There are few objects whoses compatibility level is not matched with sqlserver2005 compatibility specially when u use DTS.
Change the compatibility level to sqlserver2000 (9.0) and then try to tranfer the objects.
DTS is not as easy as it is in sqlserver2000.
from
Killer
-
Hello world,
The source is a database (replicated from a sql server 2000) which is running on sql server 2005 (with level 80 compatibily - in fact it doesn't work if i set to level 90)
The destination is a new database 2005 (level 90)
We can't transfer any table (one or more) from the source to the destination ?
The error is the same than Dinu ?
bug i think ! No ?
best regards from french riviera !
Serge
-
set the both database level to 90, than transfer. After transfering, set the source database back to 80
-
Is that so easy to switch the compatibility level from 80 to 90 and then revert back the settings? Is that so easy?
I also want to switch the database compatibility level from 80 to 90 but not sure about the affects.
If you have any updates on this please let me know.
Best Regards,
Hemant Sengar
-
Changing the compatibility level is in fact that easy. Whether you'll have bugs in the procs or elsewhere is a separate question, but if you're just transferring data manually or through SSIS, then you'll have no problems.
It's when you try to "use" the database with your front end is where the issues might come up.
So in this case, switch it, transfer and then switch it back.
Someone else can give you advise on changing it permanently. 😎
______________________________________________________________________
Personal Motto: Why push the envelope when you can just open it?
If you follow the direction given HERE[/url] you'll likely increase the number and quality of responses you get to your question.
Jason L. Selburg -
Thanks Jason for your inputs!!!
But I want to switch it permanently and would like to know what are the after affects. Some of my codes stopped functioning or there is no affect.
OR
I can change the level safely and if problem occurred can I revert back to my previous level?
-
Yes, you can revert back at any time. Whether your data's integrity has been violated is still another question.
I could have sworn that there is/was an upgrade compatibility wizard, but can't seem to find it now. I STRONGLY suggest that what ever you do, you do in a test environment. I would also wait until some other people whom have more experience in this, jump in and give you some advise.:D
______________________________________________________________________
Personal Motto: Why push the envelope when you can just open it?
If you follow the direction given HERE[/url] you'll likely increase the number and quality of responses you get to your question.
Jason L. Selburg -
If you want to permsnently change it then only one thing has to be done. Just make sure all your stored procedures use ANSI syntax.
-
Thanks Preethi !!!
-
I moved two databases from SQL 2000 to SQL 2005 using backup files.
I need to move a table from one of them to the other.
I setup a "Transfer SQL Server Objects Task" which failed with the following error:
Error: 0xC002F325 at Transfer SQL Server Objects Task, Transfer SQL Server Objects Task: Execution failed with the following error: "Version80 database compatibility level is not supported.".
Task failed: Transfer SQL Server Objects Task
Backward compatibility is installed (all options).
What goes wrong?
Are the two databases not "fully 2005" now?
Thank you,
Dinu
My answer could be a little late but I was looking for something similar and came across your question. This error could be because the Capability level of your database is not set to higher level.. You can change that by going to the database Properties and select Options change the Compatibility Level to the highest such as SQL Server 2008 (100). This should do it. Good luck
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply