Seems big, but it’s not really.
1mb x 1,000,000 queries a day (and that’s not a lot) = 1TB.
I mean, the table/result-set being transferred is only 1mb…
10 days later, and you’d better get your cost calculator out.
On premises we rarely consider network as once you have the hardware, it’s
“free”. It’s a primary source of revenue in the cloud.
Neil.
sent from my phone
On 19 Jul 2021, at 18:56, Jeff Chirco <backseatdba@xxxxxxxxx> wrote:
Thanks for the clarification about egress. I do remember now the first 10TB
being free. That seems like a big amount but it all depends on how large your
remote cloud tables are.
On Mon, Jul 19, 2021 at 10:27 AM Neil Chandler
<neil_chandler@xxxxxxxxxxx<mailto:neil_chandler@xxxxxxxxxxx>> wrote:
It's an excellent point. However, there are egress charges in OCI (although
somewhat lower than AWS/Azure). The first 10TB per tenancy per month are free.
It would not take a lot of queries with the driving site being on-prem to
gobble that up.
Neil Chandler
Database Guy.
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx>
<oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx>> on behalf
of Jeff Chirco <backseatdba@xxxxxxxxx<mailto:backseatdba@xxxxxxxxx>>
Sent: 19 July 2021 17:02
To: Kellyn Pot'Vin-Gorman <dbakevlar@xxxxxxxxx<mailto:dbakevlar@xxxxxxxxx>>
Cc: mcdonald.connor@xxxxxxxxx<mailto:mcdonald.connor@xxxxxxxxx>
<mcdonald.connor@xxxxxxxxx<mailto:mcdonald.connor@xxxxxxxxx>>;
oracle-l-freelist <oracle-l@xxxxxxxxxxxxx<mailto:oracle-l@xxxxxxxxxxxxx>>
Subject: Re: dblinks to cloud instance
That is a good point about egress. This is a MSSQL instance running on Oracle
Cloud Infrastructure actually. I don't believe there is any egress charges.
On Sun, Jul 18, 2021 at 9:58 AM Kellyn Pot'Vin-Gorman
<dbakevlar@xxxxxxxxx<mailto:dbakevlar@xxxxxxxxx>> wrote:
Hate to pile onto this, but has anyone considered the egress charges from the
cloud to onprem?
This is why I so often am moving everything to the cloud. And if this is just
the beginning, they had better look into that cost!
Hope this helps,
Kellyn
On Sat, Jul 17, 2021 at 7:49 PM Connor McDonald
<mcdonald.connor@xxxxxxxxx<mailto:mcdonald.connor@xxxxxxxxx>> wrote:
Latency is a cloud killer :-)
This is not to say it can/should not be done, but typically you'll want to give
some thought to app design to accommodate it.
eg if you're going query a table "n" times over the course of a certain time
duration, perhaps drag the table (or subset) down to the local node once into a
local table or mview, and then use it.
One risk of cross-database joins is the optimizer making the decision on where
to do the join - driving_site can mitigate this risk to some degree.
On Thu, Jul 15, 2021 at 10:46 PM Jeff Chirco
<backseatdba@xxxxxxxxx<mailto:backseatdba@xxxxxxxxx>> wrote:
What is your opinion on joining to a table over a database link that resides in
the cloud and your local database is on prem? And what if this cloud instance
is MSSQL and your local is Oracle?
We have something in the works that I just found out is supposed to go to
production next week. They are joining local and remote tables together. So far
in testing things are looking ok but the amount of data is limited right now, I
am unsure how much it will grow to.
Wondering if anyone has any experience with this.
Thanks,
Jeff
