I can't Copy a database from Sql Server 2000 to 2005

Hi,
I can't Copy a database from Sql Server 2000 to 2005. I am using the Copy
Database option from Management menu. I want to transfer all tables, and all
stored procedures. I've tried everything for the past 3 days, and it didn't
work. I always get the same error.
Below is the error that I am getting. Can someone please show/tell me a
simple permission configuration on both servers that would actually work
when I try to do the Copy Database. This would restore my attitude towards
migrating to SQL Server 2005. I don't want to have to write any scripts or
programs for that either.
I've searched all over the internet for a similar problems answered, but
couldn't find anything useful. Can you please help, because I am ready to
toss that SQL Server 2005 into a dumpster, and stay with SQL Server 2000. I
am sure that there are hundreds of users like myself with the same problem.
Can someone please answer it really well once and for all finally? I don't
want to do any Detach or backup/restore methods, or write scripts (once
again). I just want to be able to use COPY database option in the Management
menu (while the database is running) to transfer this database from SQL
server 2000 to 2005, just as I could do it in SQL Server 2000.
Can you make up a simple example to explain it. Just one simple database on
Sql 2000 with the simplest permissions, needs to be transferred to 2005.
If you can actually help me, I will be really happy, and will send you a
nice box of really good chocolates
Event Type: Error
Event Source: SQLISPackage
Event Category: None
Event ID: 12550
Date: 3/25/2007
Time: 5:31:14 PM
User: CAAA3\sqladmin999
Computer: CAAA3
Description:
Event Name: OnError
Message: ERROR : errorCode=-1073548784 description=Executing the query
"EXEC dbo.sp_changedbowner @.loginame = N'BAAA2\Administrator', @.map = false
" failed with the following error: "Cannot find the principal
'BAAA2\Administrator', 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.
You're probably better off doing a full backup then restore to the new
machine.

Regards,
Dave Patrick ...Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"Johan Garst" wrote:
> Hi,
> I can't Copy a database from Sql Server 2000 to 2005. I am using the Copy
> Database option from Management menu. I want to transfer all tables, and
> all
> stored procedures. I've tried everything for the past 3 days, and it
> didn't
> work. I always get the same error.
> Below is the error that I am getting. Can someone please show/tell me a
> simple permission configuration on both servers that would actually work
> when I try to do the Copy Database. This would restore my attitude towards
> migrating to SQL Server 2005. I don't want to have to write any scripts or
> programs for that either.
> I've searched all over the internet for a similar problems answered, but
> couldn't find anything useful. Can you please help, because I am ready to
> toss that SQL Server 2005 into a dumpster, and stay with SQL Server 2000.
> I
> am sure that there are hundreds of users like myself with the same
> problem.
> Can someone please answer it really well once and for all finally? I don't
> want to do any Detach or backup/restore methods, or write scripts (once
> again). I just want to be able to use COPY database option in the
> Management
> menu (while the database is running) to transfer this database from SQL
> server 2000 to 2005, just as I could do it in SQL Server 2000.
> Can you make up a simple example to explain it. Just one simple database
> on
> Sql 2000 with the simplest permissions, needs to be transferred to 2005.
> If you can actually help me, I will be really happy, and will send you a
> nice box of really good chocolates
> Event Type: Error
> Event Source: SQLISPackage
> Event Category: None
> Event ID: 12550
> Date: 3/25/2007
> Time: 5:31:14 PM
> User: CAAA3\sqladmin999
> Computer: CAAA3
> Description:
> Event Name: OnError
> Message: ERROR : errorCode=-1073548784 description=Executing the query
> "EXEC dbo.sp_changedbowner @.loginame = N'BAAA2\Administrator', @.map =
> false
> " failed with the following error: "Cannot find the principal
> 'BAAA2\Administrator', 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.
>
>
|||Johan Garst (Johangarst343@.yahoo.com) writes:
> I can't Copy a database from Sql Server 2000 to 2005. I am using the
> Copy Database option from Management menu. I want to transfer all
> tables, and all stored procedures. I've tried everything for the past 3
> days, and it didn't work. I always get the same error.
Are you using the Attach/Detach option, or the SMO method? The latter is
completely hopeless. I think they fixed a couple of bugs in SP2, but I
still don't find it realiable, and I question that it should have ever
been included in the final release of SQL 2005.

>Description:
> Event Name: OnError
> Message: ERROR : errorCode=-1073548784 description=Executing the query
>"EXEC dbo.sp_changedbowner @.loginame = N'BAAA2\Administrator', @.map = false
>" failed with the following error: "Cannot find the principal
>'BAAA2\Administrator', because it does not exist or you do not have
>permission.".
You *may* get past this if you first do
sp_changedbowner 'sa'
before you expoer that database, but no promises.
Dave's suggestion that simple do a BACKUP/RESTORE is definitely worth
purusing. You will have to remap users with sp_change_users_login,
and change database owner to sa, and then to the real login, but
that is not a big deal.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
|||I agree
of course, I don't think that SQL Server should have been released until
they fix the SQL Authentication problem OUT OF THE BOX
I always use attach / detach for everything, screw the copy database wizard
the punchline of course-- is that I had a windows network admin that just
REFUSED to use this methodology once upon a time... I just have basically
never had attach / detach fail on me
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns99033F7E836AYazorman@.127.0.0.1...[vbcol=seagreen]
> Johan Garst (Johangarst343@.yahoo.com) writes:
> Are you using the Attach/Detach option, or the SMO method? The latter is
> completely hopeless. I think they fixed a couple of bugs in SP2, but I
> still don't find it realiable, and I question that it should have ever
> been included in the final release of SQL 2005.
false
> You *may* get past this if you first do
> sp_changedbowner 'sa'
> before you expoer that database, but no promises.
> Dave's suggestion that simple do a BACKUP/RESTORE is definitely worth
> purusing. You will have to remap users with sp_change_users_login,
> and change database owner to sa, and then to the real login, but
> that is not a big deal.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
sql