The Vertica Forum recently got a makeover! Let us know what you think by filling out this short, anonymous survey.

Inconsistent behaviour between ADO.NET with Microsoft SQL Server and with Vertica

I've identified two distinctions between SQL Server and Vertica ADO.NET implementations:
  1. Vertica returns a result for non-query statements as part of a batch; e.g. CREATE TABLE; INSERT ...; SELECT ...; -> 3 results in Vertica, 1 in SQL Server
  2. ColumnOrdinal in the schema table returned by VerticaDataReader.GetSchema() is one-based, versus zero-based in SQL Server (note that both implementations are compliant with the ADO.NET specification)
Can you confirm if these distinctions are intentional?  Both can be worked around, although the former takes more effort in complex batches.

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file

Can't find what you're looking for? Search the Vertica Documentation, Knowledge Base, or Blog for more information.