Transfer Database Task: 2000 to 2005, but no Primary Keys are copied - Help!!

I am transferring a database from SQL Server 2000 to SQL Server 2005.  I am using 2005's Integration Services (SSIS) Transfer Database Task.  In this task, I am using the "DatabaseOnline" method.

The database transfer seemed to work, except no Primary Keys, Identity settings, Foreign Keys or Default Values transferred over!  

I have looked all over the property settings, and the internet, but I do not see any reference to including constraints.  How do I include PK, FK, etc., constraints when I use the Transfer Database Task to bring over an old SQL Server 2000 database to 2005?

LVL 1
jasonwisdomAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ved Prakash AgrawalDatabase Consultant/Performance ArchitectCommented:
Hi,
Please try transfer SQL server object task which provide all the feature which you are looking for.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
NightmanCTOCommented:
Best and most efficient way (while doing this online) is simply to take a new backup and restore this to the SQL 2005 server.

Remember to set the database compatibility level to 90 after the restore, and then updatestatistics.
0
jasonwisdomAuthor Commented:
Thank you, both.  

I am first trying the SQL Server Object Task - I'd like to keep this in a single IS package so others can just point & click & runi t.

But I'm getting an error, "Version80 database compatability level is not supported."

So far I hvaen't seen a property called Compatability Level or Version or anything like that.  Thoughts?

Thanks again.
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

NightmanCTOCommented:
Version 80 is SQL 2000. Version 90 is SQL 2005. It appears that the task cannot work against an SQL 2000 database.

Backup the database on SQL 2000 and then restore it on SQL 2005.
0
jasonwisdomAuthor Commented:
I got the compatability issue figured out, now I'm getting this message:

Error: 0xC002F325 at Transfer SQL Server Objects Task, Transfer SQL Server Objects Task: Execution failed with the following error: "ERROR : errorCode=-1073548784 description=Executing the query "DROP LOGIN [BUILTIN\Administrators]
" failed with the following error: "Cannot drop the login 'BUILTIN\Administrators', because it does not exist or you do not have permission.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
 helpFile= helpContext=0 idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}".
Task failed: Transfer SQL Server Objects Task


What...?????
I am switching to False every kind of login/permission setting I can find on the Properties.  So why is it trying to drop BUILTIN\Administrators??
0
jasonwisdomAuthor Commented:
Again, this is for the "Transfer SQL Server Objects Task".  
If I can swing this, I can get the entire database transfer into one single SSIS task.  That's my first choice.  It seems to go fairly far, except it's trying to drop logins.  

I fixed the compatability by right-clicking the 2005 Database in Management Studio, going to Properties, then Options, then chosing 9.0 for the 2005 database's compatability.  Fixed my one error.
0
jasonwisdomAuthor Commented:
OK, I figured it out.

Yes, I did use the "Copy SQL Server Objects Task".  However, I had to set about a dozen Properties.  I kept getting errors, dropping logins, creating logins, creating tables and stored procedures that already existed.....One key setting was "Copy Schema=false".

Anyway, it works.  I considered the backup / restore option, but going across versions has caused problems in the past - and it can't be automated into a simple, single SSIS task.

Thanks for your help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.