<anonymous@discussions.microsoft.com> wrote:

>Sue,
>
>Thanks for the feedback. The default did not exist in
>the destination server. Is there another way to avoid
>this error other than creating the default on the
>destination server?
>>-----Original Message-----
>>You get the error when you try to bind a default to a
>column
>>and the default object doesn't exist.
>>So...I haven't tested it to see but either you didn't
>select
>>the default to copy from the source server or if you
>did, it
>>may have done things "out of order" as in tried to bind
>the
>>column to a default and then created the default
>afterwards.
>>Did you select the default from the Select Objects
>window?
>>Did you check to see if the default named TRUE exists on
>the
>>destination server?
>>
>>-Sue
>>
>>On Fri, 4 Feb 2005 12:50:20 -0800, "Lennon King"
>><anonymous@discussions.microsoft.com> wrote:
>>
>>>I tried to copy some tables from another server using
>DTS
>>>Package Copy SQL Server Objects Task and all tables are
>>>copied over but I noticed that some of the logs has
>this
>>>error message:
>>>
>>>::Error::
>>>In file SERVER1.COGNOS_DW.BND in statement on line 4
>>>Transfer Status: Creating Column bindings on
>destination
>>>database
>>>[Microsoft][ODBC SQL Server Driver][SQL Server]The
>>>default 'TRUE' does not exist.
>>>
>>>
>>>The content on one of the BND file:
>>>
>>>setuser
>>>GO
>>>
>>>EXEC sp_bindefault N'[dbo].[TRUE]', N'[SalesTbl].
>>>[ActiveFlag]'
>>>GO
>>>
>>>setuser
>>>GO
>>>
>>>I am running SQL2K on Windows 5.2 version on the
>>>destination server. The source server has SQL2K on
>>>Windows 5.0.
>>>
>>>Question, how do you troubleshoot this type of error?
>>>
>>>TIA,
>>>Lennon
>>>
>>>
>>>
>>>
>>>
>>
>>.
>>