Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 11 to 15 of 15 total |
.Append persistence? |
Thu, Jan 3 2019 2:42 PM | Permanent Link |
Ian Branch | Tim Young [Elevate Software] wrote:
> Ian, > > Sorry, the statement logging is in 2.29, not 2.30. > > Tim Young > Elevate Software > www.elevatesoft.com Hi Tim, Thanks for the clarification. Can't use 2.29, waiting for 2.30. Regards, Ian |
Thu, Jan 3 2019 3:12 PM | Permanent Link |
Ian Branch | Tim Young [Elevate Software] wrote:
> Ian, > > << Every now and then they get an EDN Error # 300 for a Table Lock when they go to add a new record. "ElevateDB > Error #300 Cannot lock the table LineItems in the schema Default for write access." >> > > That's not a normal error - you should never see a write lock error, and if you do, it indicates a serious issue with > the underlying environment/application. EDB will wait up to ~90 seconds for a write lock, and write locks are only > held for the duration of writes (they are not something that is acquired and held across multiple operations, even > for transactions). > > However, what will block a write lock is an operation that is causing a read lock to be held on a table for a long > period of time. Un-optimized queries that perform large row scans are the common culprit, so you need to make sure > that your queries are all performing in a reasonable manner. The new statement performance logging in 2.30 is your > friend in this regard: > > https://www.elevatesoft.com/manual?action=viewtopic&id=edb2sql&topic=ENABLE_STATEMENT_LOGGING > https://www.elevatesoft.com/manual?action=viewtopic&id=edb2sql&topic=DISABLE_STATEMENT_LOGGING > > In a non-EDB Server environment, the logging will take place on a per-client-application-instance basis instead of in > a common place (the EDB Server). > > Tim Young > Elevate Software > www.elevatesoft.com Ahhhh. This I can use when 2.30 comes out. Thanks Tim. |
Thu, Jan 3 2019 3:19 PM | Permanent Link |
Ian Branch | Doing some preparation in anticipation.
IIUC, the following should retrieve the logged Statements? {sql} SELECT * FROM Configuration.Loggedstatements {sql} Regards, Ian |
Fri, Jan 4 2019 11:29 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Ian,
<< IIUC, the following should retrieve the logged Statements? >> Yes, that is correct - the LoggedStatements table is in the Configuration database. Tim Young Elevate Software www.elevatesoft.com |
Fri, Jan 4 2019 2:43 PM | Permanent Link |
Ian Branch | Thanks Tim,
App ready, code ready, just waiting for 2.30. Regards, Ian |
« Previous Page | Page 2 of 2 | |
Jump to Page: 1 2 |
This web page was last updated on Monday, May 6, 2024 at 12:23 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |