Each connection results in 2 actual connections.
One for reports, the browser/tree, and the worksheet.
A second one for bg queries used to power things like the Insight feature in
the SQL Workheet.
If you open an 'unshared' worksheet to a database - it opens a private
connection for just that worksheet that the rest of the product doesn't have
access to. I'm not sure if unshared worksheets also get the 2nd connection for
insight feature. But with unshared worksheets, each additional worksheet would
result in an additional connection.
From: Mark W. Farnham [mailto:mwf@xxxxxxxx] ;
Sent: Wednesday, June 14, 2017 9:04 AM
To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
Subject: tabs, connections, and resulting sessions from sqldeveloper
Anyone, but Jeff it you're lurking in particular: Is there a simple document
summarizing the relationship of database connections, tabs, running queries,
and so forth from sqldeveloper to the number of sessions created and held?
(Hint: I'm looking for something shorter than reading the entire concepts
guide. The target readership is impatient, would be well-served by reading the
entire concepts document, but that is unlikely to happen.)
mwf
