I believe what's happening there is that the date of 1/8/2015 that you're searching for is being expanded; therefore, the actual value the query is searching for is 1/8/2015 00:00:00.000.

To...

Although I've been in lurk-more-than-post mode lately...

Hello there, Sioban! You've been super-awesome and helpful around here, and that earns my respect ahead of anything else. I'm part of...

I believe that query won't work because your WHERE clause is quite contradictory.

Basically, you're looking for where the MONTH datepart item is both >= 11 and <= 1; mathematically, that's...

I believe the difference in those calculations will use SQL Server's numbered weeks; this will change based on your DATEFIRST settings, but, assuming a DATEFIRST of Monday:

1/11/2015 is one full...

Personally, I'd love to be a consultant someday! The idea of having a job market that's wide open and full of interesting systems and problems to solve is definitely...

I believe what you need is a FETCH NEXT just before the END in your WHILE loop:

while @@fetch_status = 0

begin

print

cast(@tid as varchar(50)) + ' ' +

cast(@min as varchar(50)) + '...

DOH! I think I was staring at the problem for way too long :-P. I missed an obvious solution; my BULK INSERT was skipping the first row, since...

Ah, of course! I remembered seeing discussion about updating the CTE to update the table of origin, but it didn't strike me as a solution here. It certainly...

Doh! My apologies; that's what I get for not triple-checking my coding :-D. Glad to know it worked out for you, though!

Rough guess here, as there isn't too much information about your table; I'd guess you have some sort of patient ID number, or something like it, to identify the fields?

If...

Hrm. It looks like you're trying to host a private server for another company's MMORPG.

I'm not entirely certain that's something SQL Server Central can help you with; it's definitely...

Steve, I hope you and all the other attendees have a good time at the Summit, packed with plenty of learning!

I've really got to attend one of the Summits one...

Oh, dear local value of $deity, this! I've had this happen twice at my current job for entirely...

My company would certainly benefit from upgrading to 2014 at this point; not so much because of new features (though in-memory could potentially be useful for one table I know...

Ah, gotcha :-). Good to see that worked. Is it possible for you to keep the variable as it originally was without the error occurring, though? Like...