Just wanted to share the following, it applies to 6.5 sp3:
After loading a set of SP-scripts with ISQL.EXE it turned out that for
several procedures the text (in syscomments table) was corrupt. What these
procedures had in common were large descriptive comment headers. Corruption
only occurred for comments in specific size ranges, e.g. 438 to 500 chars,
94? to 1006 chars, 1966 to 2012 chars.
Strangely, the corruption was not present if the same script was executed
Eventually I was able to have ISQL load the procs without corruption to
syscomments by explicitly setting the packet size to 8192 (switch '/a8192'
-- even though BOL says that *is* supposed to be the default packet size
under NT). Setting the packet size to 512 ( /a512 ) makes the problem
resurface, so maybe that is the actual default size.
Is somebody able to shed some light on what may be going on behind the
Incidentally, there is a KB article that describes similar corruption
problems for version 6.0, but does not give a workaround. . I'm surprised
this hasn't been fixed for 6.5.