Microsoft KB Archive/153969

{|
 * width="100%"|

BUG: XferMgr Does Not Preserve Nullability of User-Defined Data

 * }

Q153969

-

The information in this article applies to:


 * Microsoft SQL Server version 6.0

-

SYMPTOMS
SQL Transfer Manager does not preserve the specified nullability of user- defined datatypes. A datatype defined to allow nulls does not allow nulls after having been transferred via Transfer Manager.

CAUSE
Transfer Manager does not send the sp_addtype command with the nullability parameter surrounded by quotes. Since the nullability parameter is optional, and an unquoted NULL is simply interpreted as null, the nullability parameter is set to the default nullability of the session or database.

WORKAROUND
Generate, edit, and run the script for the user-defined datatypes. Follow this with a transfer of all other objects in the database.

STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION
For user-defined datatypes that do not allow nulls, the third parameter, nullability, is simply omitted from the sp_addtype statement, therefore, these datatypes transfer correctly.

Additional query words: 6.0

Keywords :

Issue type :

Technology : kbSQLServSearch kbAudDeveloper kbSQLServ600