Copy SQL Server Objects Fails for certain views

We have been using the 'Copy SQL Server Objects' with success for some time
to copy an entire database to another server. Recent changes to our database
infrastructure cause DTS to fail:
1) We have a check constraint which uses a user function (which refers to
the table on the check constraint
2) We have a view which refers to another view

DTS fails on both. DTS fails on the check constraint and stops. if I remove
the check constraint it will fail on the view. See errors below.

Any hints how to solve this would be appreciated.

Jonathan Orgel

Errors:
[Microsoft][ODBC SQL Server Driver][SQL Server] Invalid object n
ame
'dbo. SRS_NumberRWSubjects
'

[Microsoft][ODBC SQL Server Driver][SQL Server] Invalid object n
ame
'VMSGRECIPIENTS2'

Redefine the package.  Copy objects just uses an alphabetical order.  If you
define this to explicitly define which objects are moving, you can specify
the order which will move the dependent objects first.

--
Mike
Mentor
Solid Quality Learning
http://www. solidqualitylearning
.com


"Jonathan Orgel" <Jonathan@srssoft.com> wrote in message
news:ee1MIoJDGHA.3920@tk2msftngp13.phx.gbl...
> We have been using the 'Copy SQL Server Objects' with success for some
> time to copy an entire database to another server. Recent changes to our
> database infrastructure cause DTS to fail:
> 1) We have a check constraint which uses a user function (which refers to
> the table on the check constraint
> 2) We have a view which refers to another view
>
> DTS fails on both. DTS fails on the check constraint and stops. if I
> remove the check constraint it will fail on the view. See errors below.
>
> Any hints how to solve this would be appreciated.
>
> Jonathan Orgel
>
> Errors:
> [Microsoft][ODBC SQL Server Driver][SQL Server] Invalid object
 name
> 'dbo. SRS_NumberRWSubjects
'
>
> [Microsoft][ODBC SQL Server Driver][SQL Server] Invalid object
 name
> 'VMSGRECIPIENTS2'
>
>
>

> Redefine the package.  Copy objects just uses an alphabetical order.  If
> you define this to explicitly define which objects are moving,

Easier said than done. Our database is a constantly evolving conglomeration
of hundreds of objects. We don't relish having to constantly evolve the DTS
package as well. That's why we are using the more generic transfer
methodology to transfer the entire database, rather than identifying each
object specifically.

Also, it does not seem that objects are copied in alphabetic order, it seems
to have more to do with creation / last modification date. By making an
innocuous change to the object we are now able to complete the transfer. We
did not rename the object, yet we managed to change its transfer sequence.

Nice going Jonathan! :-)

- Joe Geretz -

"Michael Hotek" < mike@solidqualitylea
rning.com> wrote in message
news:OJOVDuNDGHA.3876@tk2msftngp13.phx.gbl...
> Redefine the package.  Copy objects just uses an alphabetical order.  If
> you define this to explicitly define which objects are moving, you can
> specify the order which will move the dependent objects first.
>
> --
> Mike
> Mentor
> Solid Quality Learning
> http://www. solidqualitylearning
.com
>
>
> "Jonathan Orgel" <Jonathan@srssoft.com> wrote in message
> news:ee1MIoJDGHA.3920@tk2msftngp13.phx.gbl... 
>
>