Re: Increasing Entry ID Length
Hi Joe, That's definitely good idea. However this will have to defined the form properties, otherwise by default the result list is sorted on the request ID. Also there are questions from user community that why the list looks different. We can take out leading zeros mentally but system can not. Still your idea is the most practical way. Best Regards, Uday Joshi Delivery Manager - BSM Tech Support Technology Infrastructure Services - BSM Unit --- Wipro Technologies, Hinjewadi, Pune 411057 India Tel: +91 20 39104092 VOIP 842-5103 From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza Sent: Thursday, September 18, 2008 01:18 AM To: arslist@ARSLIST.ORG Subject: Re: Increasing Entry ID Length ** Uday, Ron, A workaround to resolve this would be to sort the results by the Create Date rather than the Request ID.. Create Dates are usually in chronological order and there is a very very thin chance this may not be the case for consecutive requests that may have been created at about the same time... Joe - Original Message From: Uday Joshi [EMAIL PROTECTED] To: arslist@ARSLIST.ORG Sent: Wednesday, September 17, 2008 5:39:23 AM Subject: Re: Increasing Entry ID Length ** Hi Ron, I had handled such situation in earlier assignment. There to avoid huge series of leading zeros we had limited size of request ID to 6. There are few checks you will have to do 1) Check the Input length of this field. 2) Check column width of C1 at the data base level. If at database level it is 15, then you can change input length to 7 or whatever number up to 15. Since the data base is already capable of handling larger data this change has least data. If both these have length as 6 then the table needs to be altered, which may create temporary load on the system. In either case it is recommended that you do this activity in the lean time. As soon as you save the form the new ID will be generated with the new length. If you have not hit the limit you will see leading zeros. It does not affect any old records. The only visible problem is that since the request ID is stored and handled as a character the ones appended with zero comes on the top. Example 0967991 (first with 7 digits) 0967992 0967993 967988 967989 967990 (last with 6 digits) It would be a good idea to inform user community about this apparent incorrect ordering of tickets. Later on you can append leading zeros to old cases by writing direct SQL at the data base level. However you will have to take of H and B table. Best Regards, Uday Joshi Delivery Manager - BSM Tech Support Technology Infrastructure Services - BSM Unit --- Wipro Technologies, Hinjewadi, Pune 411057 India Tel: +91 20 39104092 VOIP 842-5103 From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Smith, Ron [TBC] Sent: Friday, September 12, 2008 08:23 PM To: arslist@ARSLIST.ORG Subject: Increasing Entry ID Length ** Hi all, Wanted to bounce this off the group to see if there is an easy and safe way to increase the size of the Entry-ID Field (1). We are currently at a length of six on the Homegrown helpdesk app, and after 10 + years using it, we are about to roll over ID# 99. What I want to do is to increase it to a length of 8. Problem is that the existing ID's do not pad out to the full 8 digits. Is there any utilities out there that makes this change easy and simple to do. I am pretty sure I can do this by exporting the data and massage it and reimport it, but looking for an easy way to do it. Thanks in advance. ARS 6.3 P.20 Win 2K3 SQL Server 2000 Thanks, Ron Smith Remedy/Web Developer Providence Health Services OR [EMAIL PROTECTED] 503-216-7866 DISCLAIMER: This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. __Platinum Sponsor: www.rmsportal.com http://www.rmsportal.com/ ARSlist: Where the Answers Are html___ Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any
Re: Increasing Entry ID Length
** Actually I have noticed that by changing the sort order on the form, quite a few sort orders get altered.. For eg. the sort order on active links and filters when you do set fields to find first matching entries.. that gets altered as to which entry it finds first (I learnt that once the hard way round while developing a few years ago a few versions ago).. I do not think that has changed.. I do not remember if the sort order on table fields get altered too but I think it does.. Is there some sort order you were particularly addressing that does not get altered? Joe - Original Message From: Uday Joshi [EMAIL PROTECTED]To: arslist@ARSLIST.ORGSent: Thursday, September 18, 2008 1:50:10 AMSubject: Re: Increasing Entry ID Length** Hi Joe, That's definitely good idea. However this will have to defined the form properties, otherwise by default the result list is sorted on the request ID. Also there are questions from user community that why the list looks different. We can take out leading zeros mentally but system can not. Still your idea is the most practical way. Best Regards, Uday Joshi Delivery Manager - BSM Tech Support Technology Infrastructure Services - BSM Unit --- Wipro Technologies, Hinjewadi, Pune 411057 India Tel: +91 20 39104092 VOIP 842-5103 From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouzaSent: Thursday, September 18, 2008 01:18 AMTo: arslist@ARSLIST.ORGSubject: Re: Increasing Entry ID Length ** Uday, Ron, A workaround to resolve this would be to sort the results by the Create Date rather than the Request ID.. Create Dates are usually in chronological order and there is a very very thin chance this may not be the case for consecutive requests that may have been created at about the same time... Joe - Original Message From: Uday Joshi [EMAIL PROTECTED]To: arslist@ARSLIST.ORGSent: Wednesday, September 17, 2008 5:39:23 AMSubject: Re: Increasing Entry ID Length** Hi Ron, I had handled such situation in earlier assignment. There to avoid huge series of leading zeros we had limited size of request ID to 6. There are few checks you will have to do 1) Check the "Input length" of this field. 2) Check column width of C1 at the data base level. If at database level itis 15, then you can change input length to 7 or whatever number up to 15. Since the data base is already capable of handling larger data this change has least data. If both these have length as 6 then the table needs to be altered, which may create temporary load on the system. In either case it is recommended that you do this activity in the lean time. As soon as you save the form the new ID will be generated with the new length. If you have not hit the limit you will see leading zeros. It does not affect any old records. The only visible problem is that since the request ID is stored and handledas a character the ones appended with zero comes on the top. Example 0967991 (first with 7 digits) 0967992 0967993 967988 967989 967990 (last with 6 digits) It would be a good idea to inform user community about this apparent incorrect ordering of tickets. Later on you can append leading zeros to old cases by writing direct SQL at the data base level. However you will have to take of H and B table. Best Regards, Uday Joshi Delivery Manager - BSM Tech Support Technology Infrastructure Services - BSM Unit --- Wipro Technologies, Hinjewadi, Pune 411057 India Tel: +91 20 39104092 VOIP 842-5103 From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Smith, Ron [TBC]Sent: Friday, September 12, 2008 08:23 PMTo: arslist@ARSLIST.ORGSubject: Increasing Entry ID Length ** Hi all, Wanted to bounce this off the group to see if there is an easy and safe way to increase the size of the Entry-ID Field (1). We are currently at a length of six on the Homegrown helpdesk app, and after 10 + years using it, we are about to roll over ID# 99. What I want to do is to increase it to a length of 8. Problem is that the existing ID's do not pad out to the full 8 digits. Is there any utilities out there that makes this change easy and simple to do. I am pretty sure I can do this by exporting the data and massage it and reimport it, but looking for an easy way to do it. Thanks in advance. ARS 6.3 P.20 Win 2K3 SQL Server 2000 Thanks, Ron Smith Remedy/Web Developer Providence Health Services OR [EMAIL PROTECTED] 503-216-7866 DISCLAIMER:This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you hav
Re: Increasing Entry ID Length
Hi Ron, I had handled such situation in earlier assignment. There to avoid huge series of leading zeros we had limited size of request ID to 6. There are few checks you will have to do 1) Check the Input length of this field. 2) Check column width of C1 at the data base level. If at database level it is 15, then you can change input length to 7 or whatever number up to 15. Since the data base is already capable of handling larger data this change has least data. If both these have length as 6 then the table needs to be altered, which may create temporary load on the system. In either case it is recommended that you do this activity in the lean time. As soon as you save the form the new ID will be generated with the new length. If you have not hit the limit you will see leading zeros. It does not affect any old records. The only visible problem is that since the request ID is stored and handled as a character the ones appended with zero comes on the top. Example 0967991 (first with 7 digits) 0967992 0967993 967988 967989 967990 (last with 6 digits) It would be a good idea to inform user community about this apparent incorrect ordering of tickets. Later on you can append leading zeros to old cases by writing direct SQL at the data base level. However you will have to take of H and B table. Best Regards, Uday Joshi Delivery Manager - BSM Tech Support Technology Infrastructure Services - BSM Unit --- Wipro Technologies, Hinjewadi, Pune 411057 India Tel: +91 20 39104092 VOIP 842-5103 From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Smith, Ron [TBC] Sent: Friday, September 12, 2008 08:23 PM To: arslist@ARSLIST.ORG Subject: Increasing Entry ID Length ** Hi all, Wanted to bounce this off the group to see if there is an easy and safe way to increase the size of the Entry-ID Field (1). We are currently at a length of six on the Homegrown helpdesk app, and after 10 + years using it, we are about to roll over ID# 99. What I want to do is to increase it to a length of 8. Problem is that the existing ID's do not pad out to the full 8 digits. Is there any utilities out there that makes this change easy and simple to do. I am pretty sure I can do this by exporting the data and massage it and reimport it, but looking for an easy way to do it. Thanks in advance. ARS 6.3 P.20 Win 2K3 SQL Server 2000 Thanks, Ron Smith Remedy/Web Developer Providence Health Services OR [EMAIL PROTECTED] 503-216-7866 DISCLAIMER: This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. __Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are html___ Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are ATSLogo.JPG
Re: Increasing Entry ID Length
** Uday, Ron, A workaround to resolve this would be to sort the results by the Create Date rather than the Request ID.. Create Dates are usually in chronological order and there is a very very thin chance this may not be the case for consecutive requests that may have been created at about the same time... Joe - Original Message From: Uday Joshi [EMAIL PROTECTED]To: arslist@ARSLIST.ORGSent: Wednesday, September 17, 2008 5:39:23 AMSubject: Re: Increasing Entry ID Length** Hi Ron, I had handled such situation in earlier assignment. There to avoid huge series of leading zeros we had limited size of request ID to 6. There are few checks you will have to do 1) Check the "Input length" of this field. 2) Check column width of C1 at the data base level. If at database level itis 15, then you can change input length to 7 or whatever number up to 15. Since the data base is already capable of handling larger data this change has least data. If both these have length as 6 then the table needs to be altered, which may create temporary load on the system. In either case it is recommended that you do this activity in the lean time. As soon as you save the form the new ID will be generated with the new length. If you have not hit the limit you will see leading zeros. It does not affect any old records. The only visible problem is that since the request ID is stored and handledas a character the ones appended with zero comes on the top. Example 0967991 (first with 7 digits) 0967992 0967993 967988 967989 967990 (last with 6 digits) It would be a good idea to inform user community about this apparent incorrect ordering of tickets. Later on you can append leading zeros to old cases by writing direct SQL at the data base level. However you will have to take of H and B table. Best Regards, Uday Joshi Delivery Manager - BSM Tech Support Technology Infrastructure Services - BSM Unit --- Wipro Technologies, Hinjewadi, Pune 411057 India Tel: +91 20 39104092 VOIP 842-5103 From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Smith, Ron [TBC]Sent: Friday, September 12, 2008 08:23 PMTo: arslist@ARSLIST.ORGSubject: Increasing Entry ID Length ** Hi all, Wanted to bounce this off the group to see if there is an easy and safe way to increase the size of the Entry-ID Field (1). We are currently at a length of six on the Homegrown helpdesk app, and after 10 + years using it, we are about to roll over ID# 99. What I want to do is to increase it to a length of 8. Problem is that the existing ID's do not pad out to the full 8 digits. Is there any utilities out there that makes this change easy and simple to do. I am pretty sure I can do this by exporting the data and massage it and reimport it, but looking for an easy way to do it. Thanks in advance. ARS 6.3 P.20 Win 2K3 SQL Server 2000 Thanks, Ron Smith Remedy/Web Developer Providence Health Services OR [EMAIL PROTECTED] 503-216-7866 DISCLAIMER:This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___
Re: Increasing Entry ID Length
Hi Joe, That's definitely good idea. However this will have to defined the form properties, otherwise by default the result list is sorted on the request ID. Also there are questions from user community that why the list looks different. We can take out leading zeros mentally but system can not. Still your idea is the most practical way. Best Regards, Uday Joshi Delivery Manager - BSM Tech Support Technology Infrastructure Services - BSM Unit --- Wipro Technologies, Hinjewadi, Pune 411057 India Tel: +91 20 39104092 VOIP 842-5103 From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza Sent: Thursday, September 18, 2008 01:18 AM To: arslist@ARSLIST.ORG Subject: Re: Increasing Entry ID Length ** Uday, Ron, A workaround to resolve this would be to sort the results by the Create Date rather than the Request ID.. Create Dates are usually in chronological order and there is a very very thin chance this may not be the case for consecutive requests that may have been created at about the same time... Joe - Original Message From: Uday Joshi [EMAIL PROTECTED] To: arslist@ARSLIST.ORG Sent: Wednesday, September 17, 2008 5:39:23 AM Subject: Re: Increasing Entry ID Length ** Hi Ron, I had handled such situation in earlier assignment. There to avoid huge series of leading zeros we had limited size of request ID to 6. There are few checks you will have to do 1) Check the Input length of this field. 2) Check column width of C1 at the data base level. If at database level it is 15, then you can change input length to 7 or whatever number up to 15. Since the data base is already capable of handling larger data this change has least data. If both these have length as 6 then the table needs to be altered, which may create temporary load on the system. In either case it is recommended that you do this activity in the lean time. As soon as you save the form the new ID will be generated with the new length. If you have not hit the limit you will see leading zeros. It does not affect any old records. The only visible problem is that since the request ID is stored and handled as a character the ones appended with zero comes on the top. Example 0967991 (first with 7 digits) 0967992 0967993 967988 967989 967990 (last with 6 digits) It would be a good idea to inform user community about this apparent incorrect ordering of tickets. Later on you can append leading zeros to old cases by writing direct SQL at the data base level. However you will have to take of H and B table. Best Regards, Uday Joshi Delivery Manager - BSM Tech Support Technology Infrastructure Services - BSM Unit --- Wipro Technologies, Hinjewadi, Pune 411057 India Tel: +91 20 39104092 VOIP 842-5103 From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Smith, Ron [TBC] Sent: Friday, September 12, 2008 08:23 PM To: arslist@ARSLIST.ORG Subject: Increasing Entry ID Length ** Hi all, Wanted to bounce this off the group to see if there is an easy and safe way to increase the size of the Entry-ID Field (1). We are currently at a length of six on the Homegrown helpdesk app, and after 10 + years using it, we are about to roll over ID# 99. What I want to do is to increase it to a length of 8. Problem is that the existing ID's do not pad out to the full 8 digits. Is there any utilities out there that makes this change easy and simple to do. I am pretty sure I can do this by exporting the data and massage it and reimport it, but looking for an easy way to do it. Thanks in advance. ARS 6.3 P.20 Win 2K3 SQL Server 2000 Thanks, Ron Smith Remedy/Web Developer Providence Health Services OR [EMAIL PROTECTED] 503-216-7866 DISCLAIMER: This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. __Platinum Sponsor: www.rmsportal.com http://www.rmsportal.com/ ARSlist: Where the Answers Are html___ Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any
Re: Increasing Entry ID Length
Hi, Our RRR|Chive-tool can do this for you. Here is a sample config: source_server = xxx source_tcp= source_rpc= source_user = Demo source_password = source_form = HD-form target_server = xxx target_form = HD-form qual = 1=1 entryidmode = transfertype = MOVE verifydata= YES verifyattachments = YES logfile = rrrchive.log loglevel = INFO progressbar = YES I have an unpublished utility as well that can fix up any child-records that is connected using the entry-id. Let me know if you are interested in that. Download RRR|Chive at https://www.rrr.se/cgi/rrrchive/main Best Regards - Misi, RRR AB, http://www.rrr.se Products from RRR Scandinavia: * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. * RRR|Translator - Manage and automate your language translations. Find these products, and many free tools and utilities, at http://rrr.se. Hi all, Wanted to bounce this off the group to see if there is an easy and safe way to increase the size of the Entry-ID Field (1). We are currently at a length of six on the Homegrown helpdesk app, and after 10 + years using it, we are about to roll over ID# 99. What I want to do is to increase it to a length of 8. Problem is that the existing ID's do not pad out to the full 8 digits. Is there any utilities out there that makes this change easy and simple to do. I am pretty sure I can do this by exporting the data and massage it and reimport it, but looking for an easy way to do it. Thanks in advance. ARS 6.3 P.20 Win 2K3 SQL Server 2000 Thanks, Ron Smith Remedy/Web Developer Providence Health Services OR [EMAIL PROTECTED] 503-216-7866 DISCLAIMER: This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are -- This message was scanned by ESVA and is believed to be clean. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
Re: Increasing Entry ID Length
Ron, I would think that any DBA should be able to get the job done. (And much faster than going through the ARS server.) However, while you are at it... I would suggest that you change the length back to 15 so that you never have to do this again. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap Pick two. On Fri, Sep 12, 2008 at 10:53 AM, Smith, Ron [TBC] [EMAIL PROTECTED] wrote: ** Hi all, Wanted to bounce this off the group to see if there is an easy and safe way to increase the size of the Entry-ID Field (1). We are currently at a length of six on the Homegrown helpdesk app, and after 10 + years using it, we are about to roll over ID# 99. What I want to do is to increase it to a length of 8. Problem is that the existing ID's do not pad out to the full 8 digits. Is there any utilities out there that makes this change easy and simple to do. I am pretty sure I can do this by exporting the data and massage it and reimport it, but looking for an easy way to do it. Thanks in advance. ARS 6.3 P.20 Win 2K3 SQL Server 2000 Thanks, Ron Smith Remedy/Web Developer Providence Health Services OR [EMAIL PROTECTED] 503-216-7866 DISCLAIMER: This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. __Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
Re: Increasing Entry ID Length
You may want to consider setting it to 0. We have one of our forms in our system set to 0 with a prefix. That basically gives you ISS1, ISS2, ect, and it automatically grows one character when it needs to ISS10, ISS100, ISS1000, etc. Since it sounds like your IDs are all numeric and you are approaching 99, setting it to zero should effectively cause it to roll over to 100 without any problem and it may also benefit you since you may have associations to those original IDs depending on how that home-grown app was built. If you arbitrarily go in and convert all of them and add leading zeros, you could break those associations. I'm not sure if converting an existing fixed size to 0 is possible but it could be the magic bullet you are looking for. //SIGNED// Craig Carter Software Engineer, RSP -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black Sent: Friday, September 12, 2008 11:06 AM To: arslist@ARSLIST.ORG Subject: Re: Increasing Entry ID Length Ron, I would think that any DBA should be able to get the job done. (And much faster than going through the ARS server.) However, while you are at it... I would suggest that you change the length back to 15 so that you never have to do this again. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap Pick two. On Fri, Sep 12, 2008 at 10:53 AM, Smith, Ron [TBC] [EMAIL PROTECTED] wrote: ** Hi all, Wanted to bounce this off the group to see if there is an easy and safe way to increase the size of the Entry-ID Field (1). We are currently at a length of six on the Homegrown helpdesk app, and after 10 + years using it, we are about to roll over ID# 99. What I want to do is to increase it to a length of 8. Problem is that the existing ID's do not pad out to the full 8 digits. Is there any utilities out there that makes this change easy and simple to do. I am pretty sure I can do this by exporting the data and massage it and reimport it, but looking for an easy way to do it. Thanks in advance. ARS 6.3 P.20 Win 2K3 SQL Server 2000 Thanks, Ron Smith Remedy/Web Developer Providence Health Services OR [EMAIL PROTECTED] 503-216-7866 DISCLAIMER: This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. __Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
Re: Increasing Entry ID Length
The only problem with that approach is the sort order gets messed up.. Since the Entry ID is a character field the sort order would be something like 1 10 2 3 4 5 6 7 8 9 That sort of sucks sometimes. You can sort of overcome that by changing your sort order of the form to the Create date and have the request id's sorted out on a result sequentially but there is sometimes that odd exception where the create date of two consecutive records are not what should be expected.. Joe D'Souza Remedy Developer / Consultant, Shyle Networks, New Jersey. - Original Message From: Craig Carter [EMAIL PROTECTED] To: arslist@ARSLIST.ORG Sent: Friday, September 12, 2008 1:24:15 PM Subject: Re: Increasing Entry ID Length You may want to consider setting it to 0. We have one of our forms in our system set to 0 with a prefix. That basically gives you ISS1, ISS2, ect, and it automatically grows one character when it needs to ISS10, ISS100, ISS1000, etc. Since it sounds like your IDs are all numeric and you are approaching 99, setting it to zero should effectively cause it to roll over to 100 without any problem and it may also benefit you since you may have associations to those original IDs depending on how that home-grown app was built. If you arbitrarily go in and convert all of them and add leading zeros, you could break those associations. I'm not sure if converting an existing fixed size to 0 is possible but it could be the magic bullet you are looking for. //SIGNED// Craig Carter Software Engineer, RSP -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black Sent: Friday, September 12, 2008 11:06 AM To: arslist@ARSLIST.ORG Subject: Re: Increasing Entry ID Length Ron, I would think that any DBA should be able to get the job done. (And much faster than going through the ARS server.) However, while you are at it... I would suggest that you change the length back to 15 so that you never have to do this again. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap Pick two. On Fri, Sep 12, 2008 at 10:53 AM, Smith, Ron [TBC] [EMAIL PROTECTED] wrote: ** Hi all, Wanted to bounce this off the group to see if there is an easy and safe way to increase the size of the Entry-ID Field (1). We are currently at a length of six on the Homegrown helpdesk app, and after 10 + years using it, we are about to roll over ID# 99. What I want to do is to increase it to a length of 8. Problem is that the existing ID's do not pad out to the full 8 digits. Is there any utilities out there that makes this change easy and simple to do. I am pretty sure I can do this by exporting the data and massage it and reimport it, but looking for an easy way to do it. Thanks in advance. ARS 6.3 P.20 Win 2K3 SQL Server 2000 Thanks, Ron Smith Remedy/Web Developer Providence Health Services OR [EMAIL PROTECTED] 503-216-7866 DISCLAIMER: This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. __Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
Re: Increasing Entry ID Length
Since they are all numeric, you may be able to create an associated integer field you could use for the sort but I agree, this can be a pain at times with character fields. One of the other downsides is trying to parse a Request ID like from another string (ie; subject line in an Email--which we ran into the first time ours rolled over). If you are searching for a Request ID in a string, it could be varying lengths so you can't simply assume 15 characters or in your case, 6 characters. If you are confident you are not using the existing request ids to associate with other tables/records, I'd simply increase the field size and then perform a single SQL update to prefix the correct number of zeros to all of the existing ID values. //SIGNED// Craig Carter Software Engineer, RSP -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza Sent: Friday, September 12, 2008 11:44 AM To: arslist@ARSLIST.ORG Subject: Re: Increasing Entry ID Length ** The only problem with that approach is the sort order gets messed up.. Since the Entry ID is a character field the sort order would be something like 1 10 2 3 4 5 6 7 8 9 That sort of sucks sometimes. You can sort of overcome that by changing your sort order of the form to the Create date and have the request id's sorted out on a result sequentially but there is sometimes that odd exception where the create date of two consecutive records are not what should be expected.. Joe D'Souza Remedy Developer / Consultant, Shyle Networks, New Jersey. - Original Message From: Craig Carter [EMAIL PROTECTED] To: arslist@ARSLIST.ORG Sent: Friday, September 12, 2008 1:24:15 PM Subject: Re: Increasing Entry ID Length You may want to consider setting it to 0. We have one of our forms in our system set to 0 with a prefix. That basically gives you ISS1, ISS2, ect, and it automatically grows one character when it needs to ISS10, ISS100, ISS1000, etc. Since it sounds like your IDs are all numeric and you are approaching 99, setting it to zero should effectively cause it to roll over to 100 without any problem and it may also benefit you since you may have associations to those original IDs depending on how that home-grown app was built. If you arbitrarily go in and convert all of them and add leading zeros, you could break those associations. I'm not sure if converting an existing fixed size to 0 is possible but it could be the magic bullet you are looking for. //SIGNED// Craig Carter Software Engineer, RSP -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black Sent: Friday, September 12, 2008 11:06 AM To: arslist@ARSLIST.ORG Subject: Re: Increasing Entry ID Length Ron, I would think that any DBA should be able to get the job done. (And much faster than going through the ARS server.) However, while you are at it... I would suggest that you change the length back to 15 so that you never have to do this again. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap Pick two. On Fri, Sep 12, 2008 at 10:53 AM, Smith, Ron [TBC] [EMAIL PROTECTED] wrote: ** Hi all, Wanted to bounce this off the group to see if there is an easy and safe way to increase the size of the Entry-ID Field (1). We are currently at a length of six on the Homegrown helpdesk app, and after 10 + years using it, we are about to roll over ID# 99. What I want to do is to increase it to a length of 8. Problem is that the existing ID's do not pad out to the full 8 digits. Is there any utilities out there that makes this change easy and simple to do. I am pretty sure I can do this by exporting the data and massage it and reimport it, but looking for an easy way to do it. Thanks in advance. ARS 6.3 P.20 Win 2K3 SQL Server 2000 Thanks, Ron Smith Remedy/Web Developer Providence Health Services OR [EMAIL PROTECTED] 503-216-7866 DISCLAIMER: This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. __Platinum Sponsor: www.rmsportal.com http://www.rmsportal.com/ ARSlist: Where the Answers Are html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org http://www.arslist.org/ Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers
