A picture may be worth a thousand words, but some sample data is priceless. Can't test what we can't model, so please post some. Otherwise, I doubt you...

Anything new and exciting in the new version (like screen captures/video that you can actually read)? Shame, because the rest of the book looks pretty good.

I have that book... the only thing I am not thrilled about is the quality of the videos. Going to see if it will work okay with SSIS 2012....

Maybe this will help... or not...

http://www.sqlservercentral.com/Forums/Topic1411242-149-1.aspx

From your description and table definition, I have no clue how to get what you want. What's the logic to accomplish that? To me at least, there's no...

I searched for "JSON" + "insert" here and found a ton of articles. Did you read any?

Did you add a parent row group on Itemname?

(I must be learning! I was close!)

some create table and insert scripts would go a long way to getting you a tested solution, but I would use ROW_NUMBER() to do this and not a totals query.

Something...

If a converted lead is just a property_id where there exists a move-in for that leadID, then you should be able to use EXISTS(), right?

Something like this:

SELECT lead_id

, property_id

, MIN(date_value)...

Buy a copy of Developer. It's basically the same as Enterprise, but the connections etc are limited. And it's super cheap for what you get.

If you create another calculated value in your dataset, you could do this:

=IIF(Fields!EnrollWeek.Value<=5,0

,IIF(Fields!EnrollWeek.Value<=10,6

,IIF(Fields!EnrollWeek.Value<=15,"11-15 days",16))

Because this returns an integer, you can sort on it (and it will work).

The only difference is...

WHERE fields.Name NOT IN ('sale payment', 'initial transaction')

You could do it by creating a calculated field in your dataset. Something like this:

=IIF(Fields!EnrollWeek.Value<=5,"0-5 days",IIF(Fields!EnrollWeek.Value<=10,"6-10 days",IIF(Fields!EnrollWeek.Value<=15,"11-15 days","16+ days")))

I had a dataset with numbers (EnrollWeek), so that that's what...

If your report is based on a stored procedure, it's not hard at all. Say your report is based on a parameterized stored procedure, something like

CREATE PROC GetReportData @Param1...