Wednesday, February 3, 2016

Enabling RCSI



Hello JDELIST!
This Sunday, 7 FEB, we are planning to enable RCSI in our PROD environment. It would be extremely helpful to hear about any other "go-live" experiences. Below are some questions we have. Would anyone be kind enough to share your experience with us? Thank you in advance!

Performance:

  • Did users experience any slowness in the system immediately after RCSI was enabled?
  • Did batch jobs take longer to process immediately after RCSI was enabled?
  • Did you experience slowdown when updating existing rows immediately after enabling RCSI?
  • Do you use any third party software that connects to the JDE_PRODUCTION database and if so, was there any change in performance?

Database size:
  • What is the size of your JDE_PRODUCTION (Business Data) database? (Ours is 2 terabytes)
  • How much did JDE_PRODUCTION grow after RCSI was enabled (approximately)?
  • What is the size of TEMPDB? (Ours 352G)
  • On average, how much more TEMPDB is used now that RCSI is enabled.
  • How many rows are in your F0911 table? (We have 153 million)

Configuration / Admin

  • We use transactional replication with JDE_PRODUCTION as publisher. Are you replicating and if so, have you seen any impact on replication?
  • Do you have any processes that update millions of rows (like marking records to be purged) and if so, do you have any special procedures surrounding them?
  • Please confirm the JDE.INI settings are as follows:

Enterprise Server:
SSQueryTimeout=0
SSQueryTimeoutRetries=2
WEB Server:
msSQLQueryTimeout=0
msSQLQueryAttempts=2


from JDELIST - JD Edwards® EnterpriseOne Technical http://ift.tt/1S1cNza
via IFTTT

No comments:

Post a Comment