Thank You so much for the detailed explanation.
On Sun, 11 Feb 2024 at 05:55, Peter J. Holzer wrote:
>
> Yes. Numbers in Oracle are variable length, so most Oracle tables
> wouldn't contain many fixed length columns. In PostgreSQL must numeric
> types are fixed length, so you'll have quite a lot
> On 10 Feb 2024, at 20:38, veem v wrote:
>
> Hello,
> We want to have the response time in <1 sec for our UI search query
> requirement. These will be pagination queries. These read queries will be on
> big transaction tables (will have ~500+ attributes approx will have approx.
> r
Thank you So much Greg.
Will try to test the things as max as possible. I was trying to see
basically, if any obvious things we should take care of before designing a
system for satisfying such requirements. As you pointed few things , i am
trying t answer those below
On Sun, 11 Feb 2024 at 10:43
There is a lot to unpack here. I'm going to take a quick pass, but you
ought to consider getting some custom expert help.
On Sat, Feb 10, 2024 at 2:39 PM veem v wrote:
> ... These will be pagination queries. These read queries will be on big
> transaction tables (will have ~500+ attributes appro
On 2024-02-06 11:25:05 +0530, veem v wrote:
> With respect to the storage part:- In Oracle database we were supposed to keep
> the frequently accessed column first and less frequently accessed columns
> towards last in the table while creating table DDL. This used to help the
> query
> performance
Hello,
We want to have the response time in <1 sec for our UI search query
requirement. These will be pagination queries. These read queries will be
on big transaction tables (will have ~500+ attributes approx will have
approx. rows size of ~1KB) having a continuous stream of inserts consu
