Re: [Axapta-Knowledge-Village] RecId Generation
Hi, Read this article... http://sumit-theaxfactor.spaces.live.com/blog/cns!596957786228C73F!212.entry It may answer some of your questions. Regards, Sumit On Tue, Jun 23, 2009 at 12:14 AM, tkbsmanian wrote: > > > Hi All, > > 1. How to fetch the next RecId value from the SQL query > without calling AX APIs and without updating the 'NextVal' of > 'SystemSequences' as well (as it is from in-memory pool)? > > 2. How does AOS handles RecId allocation/prevents RecId dupication, if > multiple (<249)clients connects to the same AOS and creates the > record in same table simultaneously? (i've read from one blog saying > RecId allocation is from client machine's in-memory pool of size 250) > > 3. How does AOS handles RecId allocation/prevents RecId duplication, if > more than 250 clients connects to the same AOS and creates the > record in same table simultaneously? and on what basis? > > Any info/idea on the above would highly appreciated. > > Thanks && Regards, > KBS > > >
[Axapta-Knowledge-Village] RecId Generation
Hi All, 1. How to fetch the next RecId value from the SQL query without calling AX APIs and without updating the 'NextVal' of 'SystemSequences' as well (as it is from in-memory pool)? 2. How does AOS handles RecId allocation/prevents RecId dupication, if multiple (<249)clients connects to the same AOS and creates the record in same table simultaneously? (i've read from one blog saying RecId allocation is from client machine's in-memory pool of size 250) 3. How does AOS handles RecId allocation/prevents RecId duplication, if more than 250 clients connects to the same AOS and creates the record in same table simultaneously? and on what basis? Any info/idea on the above would highly appreciated. Thanks && Regards, KBS
Re: [Axapta-Knowledge-Village] Recid
Hi, By using systemsequence class and systemsequence table Axapta create recid's. Regards, Mukesh On Wed, Sep 17, 2008 at 7:34 AM, naveed ali <[EMAIL PROTECTED]>wrote: > Hi, >I need recid for salestable,salesline& inventtrans table,I > know recid is in the Syssequences table but i don't know how to generate the > recid for above tables. > Thanks > > > -- Mukesh Mutreja # 09818421567
Re: [Axapta-Knowledge-Village] Recid
Hi, You can have a look in the below mentioned link. http://sumit-theaxfactor.spaces.live.com/blog/cns!596957786228C73F!212.entry Regards, Sumit On Wed, Sep 17, 2008 at 7:34 AM, naveed ali <[EMAIL PROTECTED]>wrote: > Hi, >I need recid for salestable,salesline& inventtrans table,I > know recid is in the Syssequences table but i don't know how to generate the > recid for above tables. > Thanks > > >
[Axapta-Knowledge-Village] Recid
Hi, I need recid for salestable,salesline& inventtrans table,I know recid is in the Syssequences table but i don't know how to generate the recid for above tables. Thanks
RE: [Axapta-Knowledge-Village] RecId Error when importing Data.
All of them. Im trying to import an enhanced LightCompany database , because an user has input some data for demonstration in the wrong db/aos, and I have to move it.. From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of KamaRaju Vudata Sent: quinta-feira, 25 de outubro de 2007 10:43 To: Axapta-Knowledge-Village@yahoogroups.com Subject: RE: [Axapta-Knowledge-Village] RecId Error when importing Data. Which table are u trying to import data into? _ From: Axapta-Knowledge-Village@yahoogroups.com <mailto:Axapta-Knowledge-Village%40yahoogroups.com> [mailto:Axapta-Knowledge-Village@yahoogroups.com <mailto:Axapta-Knowledge-Village%40yahoogroups.com> ] On Behalf Of André Santos Sent: Thursday, October 25, 2007 4:22 PM To: Axapta-Knowledge-Village@yahoogroups.com <mailto:Axapta-Knowledge-Village%40yahoogroups.com> Subject: [Axapta-Knowledge-Village] RecId Error when importing Data. Hi everybody! Im trying to import data in DAX40SP1, but when the procedure ends, it returns the following message: "An error occurred while obtaining new RecId value for the table." Has anyone passed through this? TIA, André Santos [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed]
RE: [Axapta-Knowledge-Village] RecId Error when importing Data.
Which table are u trying to import data into? _ From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of André Santos Sent: Thursday, October 25, 2007 4:22 PM To: Axapta-Knowledge-Village@yahoogroups.com Subject: [Axapta-Knowledge-Village] RecId Error when importing Data. Hi everybody! Im trying to import data in DAX40SP1, but when the procedure ends, it returns the following message: "An error occurred while obtaining new RecId value for the table." Has anyone passed through this? TIA, André Santos [Non-text portions of this message have been removed] [Non-text portions of this message have been removed]
[Axapta-Knowledge-Village] RecId Error when importing Data.
Hi everybody! Im trying to import data in DAX40SP1, but when the procedure ends, it returns the following message: "An error occurred while obtaining new RecId value for the table." Has anyone passed through this? TIA, André Santos [Non-text portions of this message have been removed]
Re: [Axapta-Knowledge-Village] RecID
Hi , Rec Id is being generated at kernel level by using system class's method xrecord.insert. If you've started the Axapta client and do the first insert, the number comes from SystemSequences table column nextval (ID -1 name SEQNO) of the dataareaID the insert will go into. Within the first insert this row is selected with an record lock in an extra sql session (to prevent rollbacking) - the number is stored somewhere as global variable within the client - then the number is increased by 25 (standard) and the record is updated. Further inserts from that client will check if already 25 insert were made - if notthe global variable is increase by one and that number will become the recid. The 26th, 51th, . insert from that client will force the reselection of SystemSequences again. If you need to assign your own recIDs, you can do that using SystemSequences class. e.g. MyTable xyz;SystemSequences obj;;obj = new SystemSequences();obj.SuspendRecIDs(tablenum(MyTable)); MyTable.overwriteSystemFields(TRUE); MyTable.clear();MyTable.RecID = 4711;...MyTable.insert; obj.removeRecIDSuspension(tablenum(MyTable)); Regards, Matrish On 1/2/06, Jayaprakash M. <[EMAIL PROTECTED]> wrote: Hi, Axapta generates Recid in a sequential order, i want to know which table and which field is involved to store the latest recid generated. Can any one give me the table name. Regards, jay Sharing the knowledge on Axapta.Visit www.frappr.com/axapta for axapta friends. SPONSORED LINKS Business finance course Business to business finance Small business finance Business finance consultant Business finance magazine Business finance schools YAHOO! GROUPS LINKS Visit your group "Axapta-Knowledge-Village" on the web. To unsubscribe from this group, send an email to: [EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. Sharing the knowledge on Axapta. Visit www.frappr.com/axapta for axapta friends. SPONSORED LINKS Business finance course Business to business finance Small business finance Business finance consultant Business finance magazine Business finance schools YAHOO! GROUPS LINKS Visit your group "Axapta-Knowledge-Village" on the web. To unsubscribe from this group, send an email to: [EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Axapta-Knowledge-Village] RecID
Hi, The RecID is generated sequentially from the Table "SystemSequences" from the System Documentation folder.. Siva. We Born to Win... Yahoo! DSL Something to write home about. Just $16.99/mo. or less Sharing the knowledge on Axapta. Visit www.frappr.com/axapta for axapta friends. SPONSORED LINKS Business finance course Business to business finance Small business finance Business finance consultant Business finance magazine Business finance schools YAHOO! GROUPS LINKS Visit your group "Axapta-Knowledge-Village" on the web. To unsubscribe from this group, send an email to: [EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Axapta-Knowledge-Village] RecID
Title: RecID Hi, Axapta generates Recid in a sequential order, i want to know which table and which field is involved to store the latest recid generated. Can any one give me the table name. Regards, jay Sharing the knowledge on Axapta. Visit www.frappr.com/axapta for axapta friends. SPONSORED LINKS Business finance course Business to business finance Small business finance Business finance consultant Business finance magazine Business finance schools YAHOO! GROUPS LINKS Visit your group "Axapta-Knowledge-Village" on the web. To unsubscribe from this group, send an email to: [EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
RE : RE : RE : [Axapta-Knowledge-Village] RecId and SysRecIdRepair
I'll try to run it on our Dev server and share the results. Steeve... -Message d'origine- De : Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] De la part de Subrahmanyam, Mamidi Envoyé : 17 juin 2005 14:06 À : Axapta-Knowledge-Village@yahoogroups.com Objet : RE: RE : RE : [Axapta-Knowledge-Village] RecId and SysRecIdRepair Well, We ran it 3 tier COnfig . but I really don't know what type of hardware ( like vendor , cluster etc etc ) the server is... Actually, MS cautioned us to run it during week ends as it may take 8 to 16 hours. But surprisingly it took only 20 minutes sometimes and 10 minutes sometimes.. Basically we have shipment/invoices come #100K dailyy..and we ran out of reciD as they started negative values just we are about to go live.. But it would be late to get the hardware details as I need to get from the NTguys. But as benchmarking type, we ran in QA environment... May be you also can give a try in tetsing company. Is there anything I can find out more for you?. Jesper Kehlet <[EMAIL PROTECTED]> wrote: Does not sound too bad, I would like to know what configuration this was being run on. Remember the properties of this is highly dependent on the hardware + configuration. From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Steeve Gilbert Sent: Friday, June 17, 2005 1:52 PM To: Axapta-Knowledge-Village@yahoogroups.com Subject: RE : RE : [Axapta-Knowledge-Village] RecId and SysRecIdRepair 20 mins for 5GB, I like that better. Thanks for your input Subbu. Steeve... -Message d'origine- De : Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] De la part de Subrahmanyam, Mamidi Envoyé : 17 juin 2005 13:47 À : Axapta-Knowledge-Village@yahoogroups.com Objet : Re: RE : [Axapta-Knowledge-Village] RecId and SysRecIdRepair Hi Steeve, How are you doing today?. Ok. I asked my admin to get the details as we ran out of RecIds. On the recommendation of MS, we ran SysRecidRepair just for one company. 1. It took 20 minutes to run ( sometimes it took 10 minutes ) the tool 2. Our Db size is very less ( Ran in a test company ) which is ~ 5GB. Good Luck. Thanks, SUbbu Steeve Gilbert <[EMAIL PROTECTED]> wrote: Thanks for your explanation Jester. Just to give me an idea, does anyone have used SysRecIdRepair? How long did it take? What was your DB size? Steeve... -Message d'origine- De : Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] De la part de Jesper Kehlet Envoyé : 17 juin 2005 11:13 À : Axapta-Knowledge-Village@yahoogroups.com Objet : RE: [Axapta-Knowledge-Village] RecId and SysRecIdRepair 1. I seriously doubt the performance increase will be significant. All it does is to renumber the existing RecIDs in a company. But it will get rid of holes in the RecID sequence, opening up to more records, and it will get rid of duplicates if any exist, clearing any issues and preparing for true PKs that you can use for e.g. replication. 2. Remember that it goes through EACH and EVERY transaction. If your DB is 18gig, you are looking at some serious downtime... I don't know if 3 weeks is an accurate number for you, but it definitely grows with the number of records in the database. It is relatively fast though compared to standard Axapta execution, as all statements are prepared and executed directly on the SQL server, not involving the Axapta ODBC/SQL connection. Although that still doesn't help you really... 3. Yes, you're right about that. If you're parent data type is RecID, it will be included. In other words: If you are doing this to repair, go ahead, if you are doing it to gain performance, you are in the wrong place... From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Steeve Gilbert Sent: Friday, June 17, 2005 8:28 AM To: Axapta-Knowledge-Village@yahoogroups.com Subject: [Axapta-Knowledge-Village] RecId and SysRecIdRepair Hi everyone, We're having performance problems with our installation. We've had a couple of hints about what could be improved and within that, we've been told that rebuilding/repair RecIds could help performance. Couple of questions on that: 1 – Is it true? Will it really help performance? 2 – We've also been told that it's time consuming. How much time consuming? Our DB is 18gigs. I remember reading 3 weeks in a recent reply in the thread "Error "RECID exists twice" when upgrading to Axapta 3.0 SP4" on [development-axapta]. If it's really 3 weeks then it's a b
RE: RE : RE : [Axapta-Knowledge-Village] RecId and SysRecIdRepair
Well, We ran it 3 tier COnfig . but I really don't know what type of hardware ( like vendor , cluster etc etc ) the server is... Actually, MS cautioned us to run it during week ends as it may take 8 to 16 hours. But surprisingly it took only 20 minutes sometimes and 10 minutes sometimes.. Basically we have shipment/invoices come #100K dailyy..and we ran out of reciD as they started negative values just we are about to go live.. But it would be late to get the hardware details as I need to get from the NTguys. But as benchmarking type, we ran in QA environment... May be you also can give a try in tetsing company. Is there anything I can find out more for you?. Jesper Kehlet <[EMAIL PROTECTED]> wrote: Does not sound too bad, I would like to know what configuration this was being run on. Remember the properties of this is highly dependent on the hardware + configuration. From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Steeve GilbertSent: Friday, June 17, 2005 1:52 PMTo: Axapta-Knowledge-Village@yahoogroups.comSubject: RE : RE : [Axapta-Knowledge-Village] RecId and SysRecIdRepair 20 mins for 5GB, I like that better. Thanks for your input Subbu. Steeve... -Message d'origine-De : Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] De la part de Subrahmanyam, MamidiEnvoyé : 17 juin 2005 13:47À : Axapta-Knowledge-Village@yahoogroups.comObjet : Re: RE : [Axapta-Knowledge-Village] RecId and SysRecIdRepair Hi Steeve, How are you doing today?. Ok. I asked my admin to get the details as we ran out of RecIds. On the recommendation of MS, we ran SysRecidRepair just for one company. 1. It took 20 minutes to run ( sometimes it took 10 minutes ) the tool 2. Our Db size is very less ( Ran in a test company ) which is ~ 5GB. Good Luck. Thanks, SUbbu Steeve Gilbert <[EMAIL PROTECTED]> wrote: Thanks for your explanation Jester. Just to give me an idea, does anyone have used SysRecIdRepair? How long did it take? What was your DB size? Steeve... -Message d'origine-De : Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] De la part de Jesper KehletEnvoyé : 17 juin 2005 11:13À : Axapta-Knowledge-Village@yahoogroups.comObjet : RE: [Axapta-Knowledge-Village] RecId and SysRecIdRepair 1. I seriously doubt the performance increase will be significant. All it does is to renumber the existing RecIDs in a company. But it will get rid of holes in the RecID sequence, opening up to more records, and it will get rid of duplicates if any exist, clearing any issues and preparing for true PKs that you can use for e.g. replication. 2. Remember that it goes through EACH and EVERY transaction. If your DB is 18gig, you are looking at some serious downtime... I don't know if 3 weeks is an accurate number for you, but it definitely grows with the number of records in the database. It is relatively fast though compared to standard Axapta execution, as all statements are prepared and executed directly on the SQL server, not involving the Axapta ODBC/SQL connection. Although that still doesn't help you really... 3. Yes, you're right about that. If you're parent data type is RecID, it will be included. In other words: If you are doing this to repair, go ahead, if you are doing it to gain performance, you are in the wrong place... From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Steeve GilbertSent: Friday, June 17, 2005 8:28 AMTo: Axapta-Knowledge-Village@yahoogroups.comSubject: [Axapta-Knowledge-Village] RecId and SysRecIdRepair Hi everyone, We're having performance problems with our installation. We've had a couple of hints about what could be improved and within that, we've been told that rebuilding/repair RecIds could help performance. Couple of questions on that: 1 ? Is it true? Will it really help performance? 2 ? We've also been told that it's time consuming. How much time consuming? Our DB is 18gigs. I remember reading 3 weeks in a recent reply in the thread "Error "RECID exists twice" when upgrading to Axapta 3.0 SP4" on [development-axapta]. If it's really 3 weeks then it's a bit? how could I say? useless? 3 ? Finally, RecId are unique within the company and not only unique only within a table (in the company), true? If so, I guess the repair WILL NOT break links made between tables with RecId like the Document Handling. Is it the same with new tables I've created? I guess it works as long as I use the EDT RecId in my tables when I refer to a RecId. Am I right here? Thanks for reading thru. I'm waiting for your answers/explanations. Steeve... Sharing the knowledge on Axapta. Sharing the knowledge on Axapta. Sharing the knowledge on Axapta. ___
RE: RE : RE : [Axapta-Knowledge-Village] RecId and SysRecIdRepair
Does not sound too bad, I would like to know what configuration this was being run on. Remember the properties of this is highly dependent on the hardware + configuration. From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Steeve GilbertSent: Friday, June 17, 2005 1:52 PMTo: Axapta-Knowledge-Village@yahoogroups.comSubject: RE : RE : [Axapta-Knowledge-Village] RecId and SysRecIdRepair 20 mins for 5GB, I like that better. Thanks for your input Subbu. Steeve... -Message d'origine-De : Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] De la part de Subrahmanyam, MamidiEnvoyé : 17 juin 2005 13:47À : Axapta-Knowledge-Village@yahoogroups.comObjet : Re: RE : [Axapta-Knowledge-Village] RecId and SysRecIdRepair Hi Steeve, How are you doing today?. Ok. I asked my admin to get the details as we ran out of RecIds. On the recommendation of MS, we ran SysRecidRepair just for one company. 1. It took 20 minutes to run ( sometimes it took 10 minutes ) the tool 2. Our Db size is very less ( Ran in a test company ) which is ~ 5GB. Good Luck. Thanks, SUbbu Steeve Gilbert <[EMAIL PROTECTED]> wrote: Thanks for your explanation Jester. Just to give me an idea, does anyone have used SysRecIdRepair? How long did it take? What was your DB size? Steeve... -Message d'origine-De : Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] De la part de Jesper KehletEnvoyé : 17 juin 2005 11:13À : Axapta-Knowledge-Village@yahoogroups.comObjet : RE: [Axapta-Knowledge-Village] RecId and SysRecIdRepair 1. I seriously doubt the performance increase will be significant. All it does is to renumber the existing RecIDs in a company. But it will get rid of holes in the RecID sequence, opening up to more records, and it will get rid of duplicates if any exist, clearing any issues and preparing for true PKs that you can use for e.g. replication. 2. Remember that it goes through EACH and EVERY transaction. If your DB is 18gig, you are looking at some serious downtime... I don't know if 3 weeks is an accurate number for you, but it definitely grows with the number of records in the database. It is relatively fast though compared to standard Axapta execution, as all statements are prepared and executed directly on the SQL server, not involving the Axapta ODBC/SQL connection. Although that still doesn't help you really... 3. Yes, you're right about that. If you're parent data type is RecID, it will be included. In other words: If you are doing this to repair, go ahead, if you are doing it to gain performance, you are in the wrong place... From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Steeve GilbertSent: Friday, June 17, 2005 8:28 AMTo: Axapta-Knowledge-Village@yahoogroups.comSubject: [Axapta-Knowledge-Village] RecId and SysRecIdRepair Hi everyone, We're having performance problems with our installation. We've had a couple of hints about what could be improved and within that, we've been told that rebuilding/repair RecIds could help performance. Couple of questions on that: 1 ? Is it true? Will it really help performance? 2 ? We've also been told that it's time consuming. How much time consuming? Our DB is 18gigs. I remember reading 3 weeks in a recent reply in the thread "Error "RECID exists twice" when upgrading to Axapta 3.0 SP4" on [development-axapta]. If it's really 3 weeks then it's a bit? how could I say? useless? 3 ? Finally, RecId are unique within the company and not only unique only within a table (in the company), true? If so, I guess the repair WILL NOT break links made between tables with RecId like the Document Handling. Is it the same with new tables I've created? I guess it works as long as I use the EDT RecId in my tables when I refer to a RecId. Am I right here? Thanks for reading thru. I'm waiting for your answers/explanations. Steeve... Sharing the knowledge on Axapta. Sharing the knowledge on Axapta. Sharing the knowledge on Axapta. __Do You Yahoo!?Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com Sharing the knowledge on Axapta. Sharing the knowledge on Axapta. Sharing the knowledge on Axapta. Yahoo! Groups Links To visit your group on the web, go to:http://groups.yahoo.com/group/Axapta-Knowledge-Village/ To unsubscribe from this group, send an email to:[EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
RE : RE : [Axapta-Knowledge-Village] RecId and SysRecIdRepair
20 mins for 5GB, I like that better. Thanks for your input Subbu. Steeve... -Message d'origine- De : Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] De la part de Subrahmanyam, Mamidi Envoyé : 17 juin 2005 13:47 À : Axapta-Knowledge-Village@yahoogroups.com Objet : Re: RE : [Axapta-Knowledge-Village] RecId and SysRecIdRepair Hi Steeve, How are you doing today?. Ok. I asked my admin to get the details as we ran out of RecIds. On the recommendation of MS, we ran SysRecidRepair just for one company. 1. It took 20 minutes to run ( sometimes it took 10 minutes ) the tool 2. Our Db size is very less ( Ran in a test company ) which is ~ 5GB. Good Luck. Thanks, SUbbu Steeve Gilbert <[EMAIL PROTECTED]> wrote: Thanks for your explanation Jester. Just to give me an idea, does anyone have used SysRecIdRepair? How long did it take? What was your DB size? Steeve... -Message d'origine- De : Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] De la part de Jesper Kehlet Envoyé : 17 juin 2005 11:13 À : Axapta-Knowledge-Village@yahoogroups.com Objet : RE: [Axapta-Knowledge-Village] RecId and SysRecIdRepair 1. I seriously doubt the performance increase will be significant. All it does is to renumber the existing RecIDs in a company. But it will get rid of holes in the RecID sequence, opening up to more records, and it will get rid of duplicates if any exist, clearing any issues and preparing for true PKs that you can use for e.g. replication. 2. Remember that it goes through EACH and EVERY transaction. If your DB is 18gig, you are looking at some serious downtime... I don't know if 3 weeks is an accurate number for you, but it definitely grows with the number of records in the database. It is relatively fast though compared to standard Axapta execution, as all statements are prepared and executed directly on the SQL server, not involving the Axapta ODBC/SQL connection. Although that still doesn't help you really... 3. Yes, you're right about that. If you're parent data type is RecID, it will be included. In other words: If you are doing this to repair, go ahead, if you are doing it to gain performance, you are in the wrong place... From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Steeve Gilbert Sent: Friday, June 17, 2005 8:28 AM To: Axapta-Knowledge-Village@yahoogroups.com Subject: [Axapta-Knowledge-Village] RecId and SysRecIdRepair Hi everyone, We're having performance problems with our installation. We've had a couple of hints about what could be improved and within that, we've been told that rebuilding/repair RecIds could help performance. Couple of questions on that: 1 – Is it true? Will it really help performance? 2 – We've also been told that it's time consuming. How much time consuming? Our DB is 18gigs. I remember reading 3 weeks in a recent reply in the thread "Error "RECID exists twice" when upgrading to Axapta 3.0 SP4" on [development-axapta]. If it's really 3 weeks then it's a bit… how could I say… useless? 3 – Finally, RecId are unique within the company and not only unique only within a table (in the company), true? If so, I guess the repair WILL NOT break links made between tables with RecId like the Document Handling. Is it the same with new tables I've created? I guess it works as long as I use the EDT RecId in my tables when I refer to a RecId. Am I right here? Thanks for reading thru. I'm waiting for your answers/explanations. Steeve... Sharing the knowledge on Axapta. Sharing the knowledge on Axapta. Sharing the knowledge on Axapta. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com Sharing the knowledge on Axapta. Sharing the knowledge on Axapta. Yahoo! Groups Links To visit your group on the web, go to:http://groups.yahoo.com/group/Axapta-Knowledge-Village/ To unsubscribe from this group, send an email to:[EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
Re: RE : [Axapta-Knowledge-Village] RecId and SysRecIdRepair
Hi Steeve, How are you doing today?. Ok. I asked my admin to get the details as we ran out of RecIds. On the recommendation of MS, we ran SysRecidRepair just for one company. 1. It took 20 minutes to run ( sometimes it took 10 minutes ) the tool 2. Our Db size is very less ( Ran in a test company ) which is ~ 5GB. Good Luck. Thanks, SUbbu Steeve Gilbert <[EMAIL PROTECTED]> wrote: Thanks for your explanation Jester. Just to give me an idea, does anyone have used SysRecIdRepair? How long did it take? What was your DB size? Steeve... -Message d'origine-De : Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] De la part de Jesper KehletEnvoyé : 17 juin 2005 11:13À : Axapta-Knowledge-Village@yahoogroups.comObjet : RE: [Axapta-Knowledge-Village] RecId and SysRecIdRepair 1. I seriously doubt the performance increase will be significant. All it does is to renumber the existing RecIDs in a company. But it will get rid of holes in the RecID sequence, opening up to more records, and it will get rid of duplicates if any exist, clearing any issues and preparing for true PKs that you can use for e.g. replication. 2. Remember that it goes through EACH and EVERY transaction. If your DB is 18gig, you are looking at some serious downtime... I don't know if 3 weeks is an accurate number for you, but it definitely grows with the number of records in the database. It is relatively fast though compared to standard Axapta execution, as all statements are prepared and executed directly on the SQL server, not involving the Axapta ODBC/SQL connection. Although that still doesn't help you really... 3. Yes, you're right about that. If you're parent data type is RecID, it will be included. In other words: If you are doing this to repair, go ahead, if you are doing it to gain performance, you are in the wrong place... From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Steeve GilbertSent: Friday, June 17, 2005 8:28 AMTo: Axapta-Knowledge-Village@yahoogroups.comSubject: [Axapta-Knowledge-Village] RecId and SysRecIdRepair Hi everyone, We're having performance problems with our installation. We've had a couple of hints about what could be improved and within that, we've been told that rebuilding/repair RecIds could help performance. Couple of questions on that: 1 ? Is it true? Will it really help performance? 2 ? We've also been told that it's time consuming. How much time consuming? Our DB is 18gigs. I remember reading 3 weeks in a recent reply in the thread "Error "RECID exists twice" when upgrading to Axapta 3.0 SP4" on [development-axapta]. If it's really 3 weeks then it's a bit? how could I say? useless? 3 ? Finally, RecId are unique within the company and not only unique only within a table (in the company), true? If so, I guess the repair WILL NOT break links made between tables with RecId like the Document Handling. Is it the same with new tables I've created? I guess it works as long as I use the EDT RecId in my tables when I refer to a RecId. Am I right here? Thanks for reading thru. I'm waiting for your answers/explanations. Steeve... Sharing the knowledge on Axapta. Sharing the knowledge on Axapta. Sharing the knowledge on Axapta. __Do You Yahoo!?Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com Sharing the knowledge on Axapta. Yahoo! Groups Links To visit your group on the web, go to:http://groups.yahoo.com/group/Axapta-Knowledge-Village/ To unsubscribe from this group, send an email to:[EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
RE : [Axapta-Knowledge-Village] RecId and SysRecIdRepair
Thanks for your explanation Jester. Just to give me an idea, does anyone have used SysRecIdRepair? How long did it take? What was your DB size? Steeve... -Message d'origine- De : Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] De la part de Jesper Kehlet Envoyé : 17 juin 2005 11:13 À : Axapta-Knowledge-Village@yahoogroups.com Objet : RE: [Axapta-Knowledge-Village] RecId and SysRecIdRepair 1. I seriously doubt the performance increase will be significant. All it does is to renumber the existing RecIDs in a company. But it will get rid of holes in the RecID sequence, opening up to more records, and it will get rid of duplicates if any exist, clearing any issues and preparing for true PKs that you can use for e.g. replication. 2. Remember that it goes through EACH and EVERY transaction. If your DB is 18gig, you are looking at some serious downtime... I don't know if 3 weeks is an accurate number for you, but it definitely grows with the number of records in the database. It is relatively fast though compared to standard Axapta execution, as all statements are prepared and executed directly on the SQL server, not involving the Axapta ODBC/SQL connection. Although that still doesn't help you really... 3. Yes, you're right about that. If you're parent data type is RecID, it will be included. In other words: If you are doing this to repair, go ahead, if you are doing it to gain performance, you are in the wrong place... From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Steeve Gilbert Sent: Friday, June 17, 2005 8:28 AM To: Axapta-Knowledge-Village@yahoogroups.com Subject: [Axapta-Knowledge-Village] RecId and SysRecIdRepair Hi everyone, We're having performance problems with our installation. We've had a couple of hints about what could be improved and within that, we've been told that rebuilding/repair RecIds could help performance. Couple of questions on that: 1 – Is it true? Will it really help performance? 2 – We've also been told that it's time consuming. How much time consuming? Our DB is 18gigs. I remember reading 3 weeks in a recent reply in the thread "Error "RECID exists twice" when upgrading to Axapta 3.0 SP4" on [development-axapta]. If it's really 3 weeks then it's a bit… how could I say… useless? 3 – Finally, RecId are unique within the company and not only unique only within a table (in the company), true? If so, I guess the repair WILL NOT break links made between tables with RecId like the Document Handling. Is it the same with new tables I've created? I guess it works as long as I use the EDT RecId in my tables when I refer to a RecId. Am I right here? Thanks for reading thru. I'm waiting for your answers/explanations. Steeve... Sharing the knowledge on Axapta. Sharing the knowledge on Axapta. Sharing the knowledge on Axapta. Yahoo! Groups Links To visit your group on the web, go to:http://groups.yahoo.com/group/Axapta-Knowledge-Village/ To unsubscribe from this group, send an email to:[EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
RE: [Axapta-Knowledge-Village] RecId and SysRecIdRepair
1. I seriously doubt the performance increase will be significant. All it does is to renumber the existing RecIDs in a company. But it will get rid of holes in the RecID sequence, opening up to more records, and it will get rid of duplicates if any exist, clearing any issues and preparing for true PKs that you can use for e.g. replication. 2. Remember that it goes through EACH and EVERY transaction. If your DB is 18gig, you are looking at some serious downtime... I don't know if 3 weeks is an accurate number for you, but it definitely grows with the number of records in the database. It is relatively fast though compared to standard Axapta execution, as all statements are prepared and executed directly on the SQL server, not involving the Axapta ODBC/SQL connection. Although that still doesn't help you really... 3. Yes, you're right about that. If you're parent data type is RecID, it will be included. In other words: If you are doing this to repair, go ahead, if you are doing it to gain performance, you are in the wrong place... From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Steeve GilbertSent: Friday, June 17, 2005 8:28 AMTo: Axapta-Knowledge-Village@yahoogroups.comSubject: [Axapta-Knowledge-Village] RecId and SysRecIdRepair Hi everyone, We're having performance problems with our installation. We've had a couple of hints about what could be improved and within that, we've been told that rebuilding/repair RecIds could help performance. Couple of questions on that: 1 – Is it true? Will it really help performance? 2 – We've also been told that it's time consuming. How much time consuming? Our DB is 18gigs. I remember reading 3 weeks in a recent reply in the thread "Error "RECID exists twice" when upgrading to Axapta 3.0 SP4" on [development-axapta]. If it's really 3 weeks then it's a bit… how could I say… useless? 3 – Finally, RecId are unique within the company and not only unique only within a table (in the company), true? If so, I guess the repair WILL NOT break links made between tables with RecId like the Document Handling. Is it the same with new tables I've created? I guess it works as long as I use the EDT RecId in my tables when I refer to a RecId. Am I right here? Thanks for reading thru. I'm waiting for your answers/explanations. Steeve... Sharing the knowledge on Axapta. Sharing the knowledge on Axapta. Yahoo! Groups Links To visit your group on the web, go to:http://groups.yahoo.com/group/Axapta-Knowledge-Village/ To unsubscribe from this group, send an email to:[EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Axapta-Knowledge-Village] RecId and SysRecIdRepair
Hi everyone, We're having performance problems with our installation. We've had a couple of hints about what could be improved and within that, we've been told that rebuilding/repair RecIds could help performance. Couple of questions on that: 1 – Is it true? Will it really help performance? 2 – We've also been told that it's time consuming. How much time consuming? Our DB is 18gigs. I remember reading 3 weeks in a recent reply in the thread "Error "RECID exists twice" when upgrading to Axapta 3.0 SP4" on [development-axapta]. If it's really 3 weeks then it's a bit… how could I say… useless? 3 – Finally, RecId are unique within the company and not only unique only within a table (in the company), true? If so, I guess the repair WILL NOT break links made between tables with RecId like the Document Handling. Is it the same with new tables I've created? I guess it works as long as I use the EDT RecId in my tables when I refer to a RecId. Am I right here? Thanks for reading thru. I'm waiting for your answers/explanations. Steeve... Sharing the knowledge on Axapta. Yahoo! Groups Links To visit your group on the web, go to:http://groups.yahoo.com/group/Axapta-Knowledge-Village/ To unsubscribe from this group, send an email to:[EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Axapta-Knowledge-Village] Recid runs negative
Can anybody shed some light urgently please!! We have a very young Axapta installation and have found that the recid's are already running negative and is being allocated towards Zero. This raises a few questions: 1 What can cause the positive id's to be 'used up' already? 2 If the recid's are not 'used up' what can cause the sign switch so early on in the life of the database (Apparently once the maximum positive number have been reached: 2,176,xxx,xxx, axapta goes to maximum negative and create from there - it does not seem likely that we have exhausted the positive numbers already) 3 Is it normal for recid's to be allocated not strictly in sequence? 4 What happens when the recid series reaches Zero? 5 If this situation is abnormal how do we correct it? Thanx everybody Yahoo! Groups Sponsor ~--> Has someone you know been affected by illness or disease? Network for Good is THE place to support health awareness efforts! http://us.click.yahoo.com/Rcy2bD/UOnJAA/cosFAA/kGEolB/TM ~-> Sharing the knowledge on Axapta. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/Axapta-Knowledge-Village/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
