Double, double, toil and trouble
Make unit test work on non-US systems
Playing my recorder... (Instrument SQL Server sequence concurrency test)

I have been unable to repro the concurrency failure (Issue #266) that we occasionally see on the CI machine. This change re-enables the test with some instrumentation such that some more information can be obtained when it next fails. To start with the information gathered is the sequence blocks actually returned from SQL Server. Hopefully this will confirm that SQL Server is never returning duplicates which then narrows the scope of the problem.
Update ATS user API.
Batching configured on the connection, not on the service collection.
Delegate table creation/deletion to DataStoreCreator.
Fluent extensions modified.
Merge branch 'ats-api' into dev
Continuing problems with the pipe... (Add small sleep to no process failure retries)

Dear SQLClient,

In our sessions together we have made significant progress in understanding your issues with finding no processes at the end of your pipe. However, in reviewing your records on the CI server I notice that you are occasionally still confused about what is in your pipe. I recommend we extend your therapy to include short periods of sleep between failed pipe usages. I know that the community generally frowns on such things, but in this case where you may potentially avoid throwing an exception (and failing the CI) I feel it is worth a try. I'll check back with you in a few weeks to see if the extra sleep has improved your mini pipe/process existential crises.

Wishing you all the best,
The Pipe Doctor
There is something rotten in the state of Denmark
Fixing unit tests breaking on da-DK systems,
due to å = aa (last letter in Danish alphabet)
Ats functional tests skip on execution, not discovery
Merge pull request #383 from aspnet/ats627

Ats functional tests skip on execution, not discovery