1 of 1 people found this helpful
The first message can be fixed by changing the size of the column referenced in SQL Configuration Manager, right click on the table and choose "Design", from there it should be apparent how to change the column.
The out of sync scans could be caused by this error in theory because if a devices scans are going to error scan because of the above error it will eventually cause the machine get "out of sync", however a few of these scans are normal.
My apologies for the rather late reply. Thank you for your suggestions. I will take a look at it and report back.
(Said it 3 times because it's THAT important)
Do NOT (EVER) change the table sizes through SQL's "Design" feature. That breaks all sorts of things (look up "ANSII PADDING" at some point).
No - use COREDBUTIL for that (and the respective DATMART.XML files). In short, what you should do is this.
1 - Make a support case with the different messages you get.
2 - We'll give you instructions on what you need to do (it's not very hard - just editing a text file for the most part).
3 - We'll be able to feed back the necessary table extensions to our own engineering group, so that you won't be running into this problem in the future.
Hope I got to this in time...
LANDesk EMEA Technical Lead.
My apologies, this is something that should only be done in extreme situation and something that is custom and only done as a last resort. Listen to Paul, he's a smart guy.
Looking at the post again I'd like to clarify something however, in SQL 2000 modifying the column to increase the size shouldn't modify the ANSI Padding, we're just adding a character size for columns that are specified smaller than the column allows, in SQL2005 the menu option would be "Modify". Never use "Table Designer" to change the table.
In best practices Paul is giving the best information though, modifying the associated XML and using coredbutil to format the column is the absolute best way to do this.
We haven't done anything yet, so don't worry. I will take Pauls suggestions in consideration when I finally have some time to look at this more closely.