oraclelover
Member²
At our site we have developers and BA's(business anaylist). Our BA's create some simple SQL scripts and run the SQL the developer's create using PL/SQL developer. The only problem they complain about is the copy to excel function, it's really slow. I have tested this on more than one computer with same results on all of them.
How to replicate
1. Run a query that will return 10,000+ rows
2. Right click on grid and pick copy to Excel.
3. Excel will open and start to be filled in with the data from the grid line by line in super slow motion.
This would not be an issue if the SQL only brought back 100 or less rows. But some of their SQL brings back anywhere from 100 to 50,000 rows of data.
Is anyone else able to replicate this issue? The computers are 1 ghz with 256 mb of RAM and 1.7ghz with 1 gig of RAM. Nothing to brag about, but more then enough to spool output to Excel.
There are ways around this by just spooling to CSV and than opening to Excel. If you spool to CSV it is fast like it should be. But that causes them to do extra steps they could avoid if they could go directly to Excel.
How to replicate
1. Run a query that will return 10,000+ rows
2. Right click on grid and pick copy to Excel.
3. Excel will open and start to be filled in with the data from the grid line by line in super slow motion.
This would not be an issue if the SQL only brought back 100 or less rows. But some of their SQL brings back anywhere from 100 to 50,000 rows of data.
Is anyone else able to replicate this issue? The computers are 1 ghz with 256 mb of RAM and 1.7ghz with 1 gig of RAM. Nothing to brag about, but more then enough to spool output to Excel.
There are ways around this by just spooling to CSV and than opening to Excel. If you spool to CSV it is fast like it should be. But that causes them to do extra steps they could avoid if they could go directly to Excel.
