As Jeff said, all was well covered while you were away, but we missed you all the same! I'm glad you got your much needed break, but I'm even more...

Enjoy your break, Steve. You deserve it!!

That was awesome!! Have a Merry Christmas, Steve!

Option 1 works only if you replace the {} with [] as follows:

df.columns = ['BillMonth', 'InvoiceAmount']

• This reply was modified 6 years, 5 months ago by Aaron N. Cutshall.

A nice reminder of how bitwise manipulation and checking work!

I don't understand. When I answered this question and selected "syntax error" I was notified that my answer was incorrect and the correct answer was "execution error" instead. Now the...

It's been a while since I've worked on SQL 2000 so I'm a bit rusty on what's allowable and what's not. I also realized that I couldn't set my 2017...

I believe that there is a solution. I'll need a bit of...

I totally agree that what the standards are defined as are not nearly as important as following them. Consistency is King!! We'll, that and good documentation.

Bugger, I didn't notice that it was a multiple answer question!

The "correlation" is that for every row in Table A, something (Action A) will be done with it (more like an OUTER APPLY because of the "every row" comment). ...

Just for giggles and grins today, I wrote a version of Jonathan's function that is similar but does not use the CROSS JOIN nor the IIF/CASE statements:

CREATE...

IMHO, the closest thing to a CROSS APPLY is a "Correlated Sub-Query" with an implicit join, which can return more than one row per input row if you're not...

Personally, I would avoid recursive CTEs whenever possible. By using the Tally, it replaces the hidden loop that the recursive CTE performs with an efficient set-based manner. Take a look...

It's true that the result is the same either way, however I prefer not to use the old method you have in your FROM statement of comma separated sources instead...