@Nick_Craver@_ArtOfCode To clarify, do you know what happens in this series of events? (1) API request is made for post 12345, which doesn't exist, at 00:00:00. (2) Post 12345 is created at 00:00:01. (3) Another API request for post 12345 is made at 00:00:04. Should request 3 hit a cache?
@Nick_Craver@_ArtOfCode Is that a new thing? We've been depending on post data being there after about 3 seconds; it's worked for the last three years.
@Nick_Craver Using <ErrorStore type="SQL" connectionStringName="MyContext"> for hookup, but no added tables to my SQL db -probably because of that error?
@Nick_Craver Still hitting this a month later - any ideas? Super weird to be seeing an order of magnitude better perf from Ruby/MySQL than ASP/SQL Server
@Nick_Craver 0ms across the board, but 55ms in SSMS' elapsed time row in the sidebar. And that's for a "select 1 as one". Posted a question, DBA/172464