RE: RE : RE : [Axapta-Knowledge-Village] RecId and SysRecIdRepair

Fri, 17 Jun 2005 11:07:35 -0700

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 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.

__________________________________________________
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

Reply via email to