@PeterVandivier [SQL Server 2019 on Ubuntu 20.04, python2 dependency removed for SQL Server 2019 across distributions.](https://techcommunity.microsoft.com/t5/sql-server/sql-server-2019-on-ubuntu-20-04-python2-dependency-removed-for/ba-p/2259118)
::: quote 2 87687 6da41129661867ded98757f884fbbd8151b27a31e604efc79bce2d85a6953da5 212,223,236 62,103,153 PeterVandivier[ *— 2 months ago*](#c87687) >> The [following commands](https://docs.microsoft.com/en-us/sql/linux/quickstart-install-connect-red-hat) for SQL Server 2019 points to the RHEL 8 repository. RHEL 8 does not come preinstalled with python2, which is required by SQL Server. Before you begin the SQL Server install steps, execute the command and verify that python2 is selected as the interpreter > >🤮 :::
https://dbfiddle.uk/?rdbms=mysql_8.0 
anyone have a theory on what i need to run to check for the existence of this function? 

It's about half way down the page, this is what you should be able to see: > timeElapsed The elapsed time for the job. This is the difference between the start datetime and the end datetime or the datetime of the current sample, if the job does not yet have an end datetime. Depending on the actual time elapsed, this field will be displayed in the format \<dddd:hh:mm:ss>.
where on that page do you see it? i'm missing it (albeit on very brisk review)
Found it mentioned [here](https://docs.itrsgroup.com/docs/geneos/5.0.0/Netprobe/ibmi/index.html). I'm guessing this is a time interval format rather than a date/time format. Of course that means that it shouldn't have a time zone indicator, and since your example does have one, then maybe the format has other uses (or someone thinks it does).
My first thought was day of the year as well, but like you, I'm unfamiliar with the format myself
don't think i'll be able to answer without seeing the string in context and the conversation seems to have moved too far past that now where i don't think i'll get it
anyone recognise this timestamp format? `0031:02:06:11.01 EST` got asked what it might be in work chat and i'm at a loss. thought it might be leading DayOfYear or something but that doesn't quite make sense
Hmm, I think I clicked the 'join' button already, that's why I don't see these.
Yes, you should see it at the top if the question pane: 
I think you can safely set SGA_MAX_SIZE high as the unused parts will be paged.
Thing is I'm currently at 56 GB / 54 GB, so I have to resize the `SGA_MAX_SIZE` anyway. But yes, I'd then increase the `SGA_TARGET` in small steps and see what happens.
it's a lot if that 1/10th is accessed much more frequently than the other 80% — but the target advice is only an estimate. You can bump it up by a smaller amount and see what gain you get, then rinse/repeat until you've got all the low hanging fruit.
So the instance is caching a approx. 1/20th of the Oracle instance in SGA (currently) which will increase to 1/10th after I change the SGA parameter.
SQL> show parameters pga; NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ pga_aggregate_limit big integer 22272M pga_aggregate_target big integer 11136M SQL>`
If the DB_TIME_FACTOR is only marginal, then I think it probably isn't related to I/O (speed-wise)
Time factor is minimal, yes, but the Physical_Reads gains is down to 1/10 th of the original reads, which is pretty impressive IMO
aren't you looking at a very marginal gain if you do? (`ESTD_DB_TIME_FACTOR=.9912`)