By all accounts, the service update seems to have gone fine. The only indication i get that things are broken is that the data is missing.
Ddi you happen to test with tens of thousands of rows of data? I suspect now that the problem is the amount of data collected by the DATESINPERIOD collection. As I understand it, that will make a unique list of dates from the column. I'm looking at cutting down the number of rows sent to DATESINPERIOD at this time.
As I mentioend, it returns results in the Desktop for any number of rows and distinct values of date that I've found. In the service it works well with a lower number of rows ( about 400 ), but fails somewhere between there and 819 rows.
When it fails, the service returns no rows, whereas the desktop works fine. When it works, the desktop and the servcie return the same number of rows.
@ericleigh007, Could you PM me so that I can get your file to investigate this bug? Sorry to see you've had such trouble getting to the bottom of this. My hunch is that it may have something to do with the NOW() in the service using NOW for whereever your data is stored vs Desktop where it's using local time on your machine.