How can we help you today? How can we help you today?

Create Table incorrectly specifies TEXTIMAGE_ON

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. :?
GavinJohnson
0

Comments

3 comments

Sort by
  • JonathanWatts
    Hi there,

    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
    JonathanWatts
    0
  • moff
    FWIW, there's a Connect bug for this
    https://connect.microsoft.com/SQLServer ... kID=328731
    moff
    0
  • Michelle T
    We've now fixed this in SQL Compare 7. There should be a new version of Packager in the next few months with SQL Server 2008 support which will have this fix in.
    Michelle T
    0

Add comment

Please sign in to leave a comment.