Query taking too much resourses on the database
-
Hi All,
The Query "INSERT INTO tdata_122 (item_id,tdata_timestamp,record_id) VALUES (:1,:2,:3)" is very expensive, it causes all sorts of problems with the Database including the creation of deadlocks and waits. Isn't there a way we can optimize it so as to make is less expensive on resources.
-
HI,
we need much more detailed problem description to attempt to fix that. This query is one of the most common (save collected DCI data). What database you are using? How big is your database and this table? Could you provide execution plan for it? Is problem only with idata_122 table or with other idata_ tables as well? Do you have active reads from that table (it could be charts refreshed very often or some scripts reading collected data)?
Best regards,
Victor
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login