Hi Stef and Cameron, Thanks for your inputs. I had completely overlooked the contact person implications. Really appreaciate that. I will test the CRM route, and see how we go. Will keep you posted on developments. Thanks once again guys. Cheers. Rajesh
--- In Axapta-Knowledge-Village@yahoogroups.com, "Cameron Robinson" <[EMAIL PROTECTED]> wrote: > > Rajesh, > > > > Along the lines Stef has stated you could setup all your active > customers as Axapta customers and the rest as CRM relations. This way > as non-active CRM relations become active you can convert them to being > a customer. > > > > Also be aware of contact details these are stored in a separate > ContactPerson table. > > > > Database logging will also impact performance so be careful. > > > > Likewise, if you need more specific input, let me know. > > > > Regards > > > > Cameron Robinson > > > > ________________________________ > > From: Axapta-Knowledge-Village@yahoogroups.com > [mailto:[EMAIL PROTECTED] On Behalf Of Stefan > Capiau > Sent: Tuesday, 30 January 2007 8:06 PM > To: Axapta-Knowledge-Village@yahoogroups.com > Subject: [Axapta-Knowledge-Village] Re: Customer Master > > > > Hi Rajesh, > > I'm working on an implementatation with currently over 4 million > customers (and over 10 million crm relations). > we are working on 3.0 SP2 with KR2 on an SQL2005 environment. > If all data belongs to one company, you should be considering removing > the dataareaid as first keyfield in the indexes (you can do this with > settings on the AOS). It is also advisable to let sql decide which > indexes to use. > Be aware when you are using Record Level Permission functionality. > This can give strange instructions towards SQL server. > > If you need more input on specific issues, please let me know. > > Regards, > Stef > > --- In Axapta-Knowledge-Village@yahoogroups.com > <mailto:Axapta-Knowledge-Village%40yahoogroups.com> , "Rajesh" > <rajeshtalpade@> wrote: > > > > Hi All, > > I am just about to implement V3.0 (SQL d/b) on a client, who has a > > customer master of 1.3 million records. . . . > > Does anyone have any experience with this size of customer master > > table, and are there any known issues that one needs to be > > aware/mindful of. > > Appreciate any feedback. > > Cheers. > > Rajesh > > > > > > > In operation for more than a century, The Perth Mint is the proud winner of > six Marketing and Design Excellence Awards in recognition of continued > innovation and minting excellence. With a treasure trove of unique > attractions housed on its heritage site in East Perth, The Perth Mint is a > multi-award winning tourist destination, winning gold at the 2006 Western > Australian Tourism Awards. > > **************************************************************************** > This email, together with any attachments, is intended for the addressee > only. It may contain confidential or privileged information. If you are not > the intended recipient of this email, please notify the sender, delete the > email and attachments from your system and destroy any copies you may have > taken of the email and its attachments. Duplication or further distribution > by hardcopy, by electronic means or verbally is not permitted without > permission. > > While every care has been taken, The Perth Mint cannot be held responsible > for any statistic, statement or representation made in this email. The > Perth Mint cannot accept liability for any loss suffered as a result of any > action of any kind whatsoever taken by any person based on information in > this email. > **************************************************************************** > > > [Non-text portions of this message have been removed] >
