Re: Questions about SQL*Developer CLI for exporting data

The database is 300 TB, but there is a lot of HCC and BASIC/OLTP table compression in use, so the estimated size of the exported CSV files is 1.25 PB of text.

On 12/13/2020 10:42 AM, Mladen Gogala wrote:
> Hi Tim!
> 1.25 PB? With "P" as in  "Peta"? Wow! I have never worked with a
> database that large. The largest database I have worked with was 450
> TB, which is less than half of the monster you're dealing with. 
> Please, summarize the challenges on your web page when possible. I am
> very interested in the challenges you'll doubtlessly meet during the
> course of the project. Something tells me that I'm not the only one
> here with such an interest.
> Regards
>
> On Sun, Dec 13, 2020 at 1:30 PM Tim Gorman <tim.evdbt_at_gmail.com
> <mailto:tim.evdbt_at_gmail.com>> wrote:
>
> Not floppies, but several Azure Data Box Heavy
> <https://azure.microsoft.com/en-us/pricing/details/databox/gateway/>
> will be used for this task, which should be a little faster than
> the two weeks it would take to push 1.25 PB over a 10 Gbps network
> link.
>
> However, since the customer has decided not to upgrade their 200
> Mbps link to 10 Gbps, the Data Boxes should be much faster than
> the 652 days it would otherwise to push that 1.25 PB.
>
> Or so we hope...
>
>
>
> On 12/12/2020 9:38 PM, Mladen Gogala wrote:
>> You can still export data to floppy disks and send them Microsoft
>> by snail mail. Neither sleet nor snow...
>>
>> The only problem is where to buy floppies. I haven't seen them in
>> stores for a while now. I am preparing my own letter to
>> Microsoft. I've been a good boy throughout the year and I deserve
>> some presents.
>>
>> On 12/12/20 1:13 AM, Norman Dunbar wrote:
>>> Tim, et al,
>>>
>>> Due to security, there was no way we were allowed a network
>>> connection between current production and Azure.
>>
>
>
>
> --
> Kindest regards,
> Mladen Gogala
>

--
http://www.freelists.org/webpage/oracle-l