var tupleList = new List<(string Firstname, string Lastname)>
{
( "Peter", "Rasmussen" ),
( "John", "Doe" )
};

string_split()

    command.ExecuteNonQuery();

When handling batch SQL statements that return multiple results, the implementation of FillSchema for the OLE DB .NET Data Provider retrieves schema information for only the first result. To retrieve schema information for multiple results, use Fill with the MissingSchemaAction set to AddWithKey.

using var con = new SQLiteConnection(cs);

Besides the visible performance advantage over the other solutions, we can also easily tweak the behavior with some Options.

There are few major advantages of using a database table as logging destination, such as:

It provides the ability to use all DBMS constructs to query, filter, and summarize the information available. It is as good as any other transaction table and you can use the information available in the best possible manner.
Maintenance becomes much easier with DB tables such that you can delete rows with unwanted information by simply writing a query. You can easily identify rows with unwanted data and delete these selectively. Alternatively, you can also schedule a DB job which deletes information more than 3 months old, etc. And many similar possible approaches as you would otherwise use with a database table.
There are some disadvantages of using a database table as logging destination and hence, it would not be a recommended approach if: