Improved performance dealing with missing messages   Prior to SQL Remote version 12.0.1, if the consolidated database terminated before all the messages in a multi-part message were received, the remote database would delete all the received messages and send a resend request to the consolidated database. The consolidated database would then scan the applicable transaction log to satisfy the resend request. With SQL Remote version 12.0.1, on startup, SQL Remote will generate a warning message about missing messages, delete the existing messages, and ask for a resend only if it has seen a message that contains a commit and that is the last part of the multi-part message, or that is the next message after the previous multi-part message.