Options
Create Table incorrectly specifies TEXTIMAGE_ON
GavinJohnson
Posts: 6
SQL PACKAGER PROBLEM
This problem occurs when a table that had a Text column has it removed.
The issue, I believe, is caused because SQL Server 2005 does not cleanly remove all references to the lob_data_space when it is ceased to be used.
I'm guessing that the script engine uses sys.tables and this incorrectly leaves the lob_data_space_id set to 1 [PRIMARY] where it should be 0 after all text columns have been removed from the table.
I'd say this was a Microsoft issue, except their retort would be that the script of the table from Management studio successfully manages to not generate the erroneous TEXTIMAGE_ON clause. :?
This problem occurs when a table that had a Text column has it removed.
The issue, I believe, is caused because SQL Server 2005 does not cleanly remove all references to the lob_data_space when it is ceased to be used.
I'm guessing that the script engine uses sys.tables and this incorrectly leaves the lob_data_space_id set to 1 [PRIMARY] where it should be 0 after all text columns have been removed from the table.
I'd say this was a Microsoft issue, except their retort would be that the script of the table from Management studio successfully manages to not generate the erroneous TEXTIMAGE_ON clause. :?
Comments
Perhaps we should be doing some extra checking of tables, in the same what that SSMS does, this would then get around the problem. I will raise an issue for this to be fixed in a future version of SC.
Regards,
Jonathan
-Project Manager
-Red Gate Software Ltd
https://connect.microsoft.com/SQLServer ... kID=328731
Redgate Software