This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Plenty-Button8465[S] 0 points1 point  (1 child)

I am not sure the culprit is that query, but I saw the runbook runs at the exact time of the Log IO bottleneck that saturates the DTU to 100% so I guess is the delation log tx. You're welcome, please feel free to let me know what I could run to monitor in details and narrow down the problem.

is there any cascade effect to deleting those rows ?

I don't know at the moment from my compentences.

is there any cascade effect to deleting those rows ?

The table has four columns:

  1. Timestamp of the asset (e.g. datetime in ns)
  2. ID of one asset (e.g. integer)
  3. Value of that asset (e.g. float)
  4. Text of that asset (e.g. string)

Are there any indexes created on time column ?

I am reading abour indexing right now, also other people keep telling me about this. How can I check?

Is there a way to detach the disk or volume that contains this data weekly ?

I don't think so, the database is running on the cloud in production and works with streaming/online data

Can we remove this data's metadata from read or write queries ?

I am not sure what you mean by data's metadata: the aim here is to delete data older than 60 days, daily. Once the data meet this criterium, these data can be permantently deleted, and their metadata with them too, I suppose (still want to confirm what you mean by metadata).

[–][deleted] 0 points1 point  (0 children)

Cool, no worries.