In our case, yes, the majority are from Join forms. But we still have a lot of those fields that are on regular forms with the DB length being smaller then the Remedy length. I do not recall any issues (yet), but as someone else said, it is something to keep in mind in case we do encounter an issue.
Thank you, Pascale Sterrett [email protected] Sent by: [email protected] 02/23/2012 12:21 PM Please respond to [email protected] To [email protected] cc Subject Re: Not Matching Lengths ** So are most of you seeing this on join forms? Just curious, we ran into a problem with form corruption a while back when we imported a join form from one environment to another. It was enough corruption that it required a complete DB restore to correct the issue. We have since just adopted a rule that we would not import join forms… ever. I wonder if this little oddity could be the culprit. From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of JD Hood Sent: Thursday, February 23, 2012 1:11 PM To: [email protected] Subject: Re: Not Matching Lengths ** On a 7.6.04p2 ITSM Pre-Config Stack Installer environment (MS SQLServer) There's 931 fields with different lengths. Exactly 100 of those fields have a DB length less than ARS length and a quick scan through that list looks like all of those are joins. But, no DB weirdness has manifested, so I'll just tuck this away in the back of my mind and nervously whistle past the graveyard. Thanks, JDHood On Thu, Feb 23, 2012 at 1:14 PM, LJ LongWing <[email protected]> wrote: ** Those would be of upmost concern to me…because if Remedy thinks it can insert 200 chars, but the DB can only handle 150…that’ll cause issues. From: Action Request System discussion list(ARSList) [mailto: [email protected]] On Behalf Of Andrew C Goodall Sent: Thursday, February 23, 2012 10:40 AM To: [email protected] Subject: Re: Not Matching Lengths ** I ran the query and returned 878 rows. I’m not too concerned with the ones where the RemedyMaxLength is smaller than the DBMaxlength, but I am concerned about the ones where the DBMaxlength is less than the RemedyMaxLength – it’s those that could cause fatal errors / crashes. I modified your query to fc.maxLength > c.CHARACTER_MAXIMUM_LENGTH And still returned 81 rows. However, looking at this further I think many of these are join forms and the query isn’t reflecting the correct size on the originating form? ARS 7.5.4 system with Atrium CMDB 7.5 ITSM 7.5.01, SLM 7.5, SRM 7.6. Small amount of custom form apps. Regards, Andrew Goodall Software Engineer 2 | Development Services | jcpenney . www.jcp.com From: Action Request System discussion list(ARSList) [mailto: [email protected]] On Behalf Of [email protected] Sent: Thursday, February 23, 2012 11:31 AM To: [email protected] Subject: Re: Not Matching Lengths ** Seeing the same issue on all 9 servers. This is from one of them AR System Email User Instruction Templates Short Description 60 254 AR System Email Templates Short Description 60 254 AR System Email Messages Short Description 60 254 AR System Email Mailbox Configuration Short Description 60 254 AR System Email Instructions Short Description 60 254 AR System Email Instruction Parameters Short Description 60 254 AR System Email Error Logs Short Description 60 254 AR System Email Attachments Short Description 60 254 AR System Email Association Short Description 60 254 FB:History Short Description 128 254 FB:Alarm Events Monitor ID 15 254 ReportType Short Description 128 254 ReportSelection OriginalFormServer 128 254 AR System User Preference Short Description 128 254 AR System User Central File Short Description 128 254 AR System Administrator Preference Short Description 128 254 User Password 30 255 Server Statistics Short Description 3 254 Server Events Unused_Descr 3 254 Alert Events UNUSED 5 254 AR System Currency Ratios Short Description 4 254 AR System Currency Label Catalog Short Description 4 254 AproposSalesCoordQueueRelate Sales Coordinator 2 255 Business Time Holidays Tag 128 254 Thank you, Pascale Sterrett If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation. _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If the reader of this message is not the intended recipient, you are hereby notified that your access is unauthorized, and any review, dissemination, distribution or copying of this message including any attachments is strictly prohibited. If you are not the intended recipient, please contact the sender and delete the material from any computer. _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
