IN_SOH SerialNumber Increase

[2can2]

Hi, I am I using the SerialNumber in IN_SOH to track a number of collection results and Names and want to extend the Field size from 50 to say 70! The restrictions now won't let me do this without dropping and recreating the File BUT I wanted to check if there would be any system implications if I did this?

In a similar vain, I want to extend the IN_BinLocationLookup.ShortName field from 10 to 20. I don't think this is used anywhere else in the system except the Warehouse Maintenance so hopefully should not cause any issues?

Your advice please and if ok what is the best method of extending these fields. Cheers

[Mike.Sheen]

Hi, I am I using the SerialNumber in IN_SOH to track a number of collection results and Names and want to extend the Field size from 50 to say 70! The restrictions now won't let me do this without dropping and recreating the File BUT I wanted to check if there would be any system implications if I did this?

In a similar vain, I want to extend the IN_BinLocationLookup.ShortName field from 10 to 20. I don't think this is used anywhere else in the system except the Warehouse Maintenance so hopefully should not cause any issues?

Your advice please and if ok what is the best method of extending these fields. Cheers

In a cursory examination of the application code, you should be safe to extend the SerialNo field of IN_SOH to up to 255 characters. Reports which use stored procedures and utilising memory or temporary tables may be an issue - I've not looked at stored procs - but if any issues occur you could always edit them to match - with the caveat that each upgrade our stored procedures will be updated to the model stored procedures and will undo any such modifications.

The same applies to IN_BinLocationLookup.ShortName - anything up to 255 characters should, in theory, work.

The original restriction for 50 characters in the IN_SOH table for the SerialNo field is mostly legacy reasons - originally SQL Server had a hard limit of 8060 bytes per row (and there was conscious effort to stay within that limit and to leave adequate space for future revisions of the tables), but that limit is now a bit softer, however there may be potential performance impacts going beyond that limit. In earlier versions of Jiwa, some tables were split into 2 because of this limit (DB_Main used to be DB_Main and DB_Main2 because of this 8060 byte limit).

Changing our tables is possible for a future release but there is a risk we may introduce a performance penalty by doing so - we've not done any testing or benchmarking - so if you opt to, do so at your own risk.

I've logged bugs 12492 and 12493 to expand the IN_SOH.SerialNo and IN_BinLocationLookup.ShortName fields to be 255 characters (bytes).

[2can2]

Thanks Mike. Very useful especially when these fields are extended.