For SQL Server, a DML command (like INSERT) is always transaction-protected. If something goes wrong while processing that command, then the whole transaction is rolled back. All or nothing.
Note that there is a difference here from the various bulk-loading options. Those includes BULK INSERT command, BCP.EXE, SqlBulkCopy class and SSIS. For such tools, you ...
For SQL databases that are ACID - A is for Atomic meaning all or none of a transaction will occur. When partial data is loaded and the connection stops, there is no choice in a ACID constraint but to drop all of the data.
For MySQL Innodb (default) is ACID but there is a MyISAM engine which isn't.
as per the comment by Dominique Boucher those number seems to be indication of time, as per the picture below they vary.
"The duration spent..." I would assume that those number are the time
spend (probably in milisecond) to do the initialization and the
handshake (an not port number)...
I don't think you can get that from the database server side. The tnsnames.ora file is local to the client, so you could have a net service name (connection name) of 'ORANGE' that connects to a database service called 'BANANA'.
I had a look at some of our listener log files, and they don't have this info. The SYS_CONTEXT function exposes a lot of info but ...