jslusher (9/22/2014)
The solution turned out to be adding this to the query:SET ANSI_DEFAULTS ON;
Apparently the gem does not account for that.
Fair enough. That would have been a piece of the next group of things I would have recommended to check. Connection settings like ansi_defaults, ansi_nulls, ansi_null_dflt_on, ansi_padding, ansi_warnings, arithabort, concat_null_yields_null, quoted_identifier, transaction_isolation_level.
Glad it is working tho.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events