What is the Clone Cursor Options for on the SaveAs dialogs in the Schema Browser and (SQL) Editor?
When “Clone Cursor” is turned OFF, and a user goes to the “save as” screen and begins an export, we use the actual cursor which is tied to the data grid. The advantage to this is that the query does not need to be re-executed. The disadvantage to this is that the whole dataset must be held in your PC’s RAM, because this is a scrollable dataset (it is this mechanism that allows scrolling in the grids). When “Clone Cursor” is turned ON, and a user goes to the “save as” screen and begins an export, we create a new, non-scrollable cursor. The advantage here is that as rows are read in and sent to the destination file, we don’t have to hold them in memory any longer…and a minimal amout of RAM is used. The disadvantage is that for this to happen, the query must be re-executed. So…which setting should you use? If your query returns a LOT of rows (too many to hold in your PC’s RAM), you should have “Clone Cursor” turned ON…even if your query takes a long time to execute. If your query re
