SQL Packager tries to catch as many known exception types as it can and tries to construct helpful error messages. Unfortunately, what you are seeing is a software bug, probably caused when trying to create a data script for a table that has a large object and no primary key. SQL Packager should support this, at least when creating a new database package or adding a new table to an existing database.
The only workaround I know of at this time would be to choose one or more columns that can be used to uniquely identify rows of data and create a primary key or unique index or constraint on those column(s).
This query should help you identify the tables that need modification:
- Code: Select all
SELECT O.[NAME] as [Table name], C.[NAME] as [Column Name]
FROM SYSOBJECTS O
JOIN SYSCOLUMNS C
ON C.ID = O.ID
WHERE O.XTYPE = 'U'
AND C.XTYPE in (34,35,99) /*IMAGE,TEXT,NTEXT*/
and O.name !='dtproperties'
ORDER BY O.[NAME], C.[NAME]