Hello, Before asking my noob questions, here are the contexts : Few months ago, we got disk usage issues (especially the workspace), to fix it, the administrators decided to move all our workspace to an other disk, mainly dedicated to archived data (we do not know how are the velocity of these disks, we also do not know if there are any others settings to pay attention on too, that could explain the weird behaviour below - 0 visibility as final user). We only have noticed few weirds behaviours, with the same SQL and/or datastep (i.e. same code) : - the calculations are extremely slow (x3 in term of time) - the final size of tables increase insanely (x10 in term of size) Could it be server side issue? I mean, could it be related to the disk properties? For the slowing of calculations because of I/O I could understand, but why the size of table also increases? I have already done a quick test, the sum of the data is the same, same before and after (same for the total of observations), but not the same size... And above all, the code is the same... so why? I am not administrator, so I have no clue at all, any suggestions/feedbacks are welcome Thank your for reading
... View more