That wouldn't be the right thing to do, if the customers are the ones you are tracking your incidents, problems etc. By definition, customers would mean that.. Maybe you can extend your idea to have an archive form to the People form to take off obsolete customer records from the people form once they are not your customers anymore.
Joe From: Siddiqi, Wirasat (Contractor) Sent: Thursday, October 07, 2010 1:15 PM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: Re: 4.6 million records in people form ** I think SQL Server allows 8KB per row. So, space should not be a big issue. However, you need to check with your DBA. If 4.6 million are customers and not the user, I would suggest creating a separate table for them instead of storing them in CTM:People form. Because, CTM:people is referenced with so many tables and workflow and that might create the performance issue. -------------------------------------------------------------------------------- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Joe Martin D'Souza Sent: Thursday, October 07, 2010 12:44 PM To: arslist@ARSLIST.ORG Subject: Re: 4.6 million records in people form ** In ITSM 7.1 I have come across no known bugs with querying the CTM:People form from anywhere within the application, either through workflow, or other queries designed... So the question is more about any customization that you may have done that may retrieve information from the CTM:People form to be set somewhere. Make sure that the searches that are issued on such customization, are using appropriate indexes, and if not, rebuild those qualifications if possible around existing indexes, or create new indexes as appropriate to support those queries.. Respect this one cardinal rule, and you should be ok.. Joe From: Mr. Tee Sent: Thursday, October 07, 2010 4:47 AM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: 4.6 million records in people form ** Hi ARSLIST, I am thinking about importing all customers (4.6 million) into Remedy (ITSM 7.1). The customers should not be users but only people. There will only be about 300 users and that is no problem. The Remedy applications and database is running on separate servers. The DB server is MS SQL 2005. Do anybody have any experience about setup and performance with this amount of records in the people form ? Lookup in ITSM applications (Customer on incident form, Requester on Change form etc) ? Thanks in advance. Kind regards Mr. Tee _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
