Daniel Theophanes

That could be. In your tests you describe a number of network hops and TDS is somewhat chatty.

This change alters renames a number of existing fields. Please revert. Please also document what type of values this accepts, include in comments with examples of what this solves.

Those are fair points. I wasn't even aware of the mentioned CL. We should probably see about adding a test for this and updating the README.

Please be aware that there is no 100% correct way with SQL server to return a LastInsertID without modifying the SQL and returning it in the select statement. If you...

Not magical, each connection is a unique session. calling db.Conn(), then calling exec then scope_identity on the same connection is what you want to do. Making a Tx is another...

There is no such thing as "exec" in SQL Server. Exec for the DB interface just means disregard all rows. Don't use Exec. Use Query. Scan the first row to...

@simenfd Can you link to official docs in the TDS documentation?

Great to see it, but I want to wait until the first one is settled a bit more.

@fhquthpdw Don't do this. If your parameters are strings, you must escape the value, which is a simple function, but must be done. Alt, you can run: `db.Query("sp_name", sql.Named("Param1", value1),...

I don't see how this can be correct. This is effectively truncating all characters to ASCII `byte(vr[i])`. It looks like you are mostly just removing any Unicode characters from the...