RE: Re: Memory change possible with TOAD 11

64-bit would not have solved your issue - i.e. it's not some magic silver bullet. When you want to bulk load data you should be using the right method - e.g. sql loader, external tables, or some third party bulk load or etl tool. A 64-bit toad would have only allowed you to try a brute force solution longer before having the same issues. When you need to dig a swimming pool a back hoe is always preferable to a shovel - no matter how big or nice the shovel. Manual or brute force only works to a point - 64-bits won't fix that ....


From: [email protected] [mailto:[email protected]] On Behalf Of Gerald N
Sent: Monday, October 17, 2011 5:55 PM
To: [email protected]
Subject: [toad] Re: Memory change possible with TOAD 11



Actually, I was doing it with TOAD import rather than CTL creation
Once I used the CTL creation, it loaded the 16 million records extremely fast with no issues.
hmmmm.
We'll see.

TOAD 64 coming soon?.... anyone?

--- In [email protected]<mailto:toad%40yahoogroups.com>, "Simoneau, Roger" <rsimonea@...<mailto:rsimonea@...>> wrote:
>
> >> Windows 7 Ulitmate machine. The machine has 8 G memory,
> >> so I thought I would give Oracle 3.6G
>
> Wow... does that mean Windows 7 Ultimate requires the other 4.4 G of memory? Ouch!
>
> Roger S.
>
> ________________________________
> This communication, including any attached documentation, is intended only for the person or entity to which it is addressed, and may contain confidential, personal and/or privileged information. Any unauthorized disclosure, copying, or taking action on the contents is strictly prohibited. If you have received this message in error, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply.
>