Stairway to T-SQL DML Level 8: Using the ROLLUP, CUBE and GROUPING SET operator in a GROUP BY Clause

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss Content Posted by Gregory Larsen » Stairway to T-SQL DML Level 8: Using the...

Stairway to T-SQL DML Level 8: Using the ROLLUP, CUBE and GROUPING SET operator in a GROUP BY Clause

Rate Topic

Display Mode

Topic Options

Author

Message

Greg Larsen

Posted Tuesday, January 10, 2012 9:55 AM

Ten Centuries

Group: General Forum Members
Last Login: Saturday, January 19, 2013 8:28 AM
Points: 1,038, Visits: 255

Comments posted to this topic are about the item Stairway to T-SQL DML Level 8: Using the ROLLUP, CUBE and GROUPING SET operator in a GROUP BY Clause

Gregory A. Larsen, MVP

Need SQL Server Examples check out my website at http://www.sqlserverexamples.com

Post #1233364

subramanian.rajan

Posted Tuesday, August 21, 2012 11:39 PM

Grasshopper

Group: General Forum Members
Last Login: Thursday, August 23, 2012 5:36 AM
Points: 10, Visits: 29

Greg Larsen (1/10/2012)

Comments posted to this topic are about the item <A HREF="/articles/Stairway+Series/87629/">Stairway to T-SQL DML Level 8: Using the ROLLUP, CUBE and GROUPING SET operator in a GROUP BY Clause</A>

It is an amazing article on the Rollup, Cube and Grouping SEt operators. Excelling explanation and very good presentation with very simple example.

Post #1348188

dbuendiab

Posted Wednesday, August 22, 2012 12:39 AM

SSC Journeyman

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 11:41 AM
Points: 77, Visits: 218

Good article, but I've been surprised with the use of COALESCE() for getting the 'Grand Total' in Listing 3. I think it's better to use the GROUPING() function to know if we are dealing with a subtotal row, and then replace the NULL with the correct label. If you use COALESCE() and there is some NULL value in the column CheckFor, you'll get a mistaken label.

Post #1348204

BarneyL

Posted Wednesday, August 22, 2012 1:41 AM

Old Hand

Group: General Forum Members
Last Login: Thursday, May 16, 2013 4:05 AM
Points: 318, Visits: 640

Thanks for this, it's a good clear summary of these features.
Are there any performance gains to be had by switching to use these features over unioning a set of SQL statements together? If so I have a few reports that might benefit from rewriting to use them.

Barney

Post #1348220

brichardson 56244

Posted Wednesday, August 22, 2012 9:23 AM

Forum Newbie

Group: General Forum Members
Last Login: Tuesday, April 09, 2013 3:12 PM
Points: 2, Visits: 12

Nice article! I had never really thought much about using those powerful options with GROUP BY, but now I will use them more.

--Bill

Post #1348508

JGBW12

Posted Wednesday, August 22, 2012 2:18 PM

Forum Newbie

Group: General Forum Members
Last Login: Monday, August 27, 2012 7:07 AM
Points: 1, Visits: 4

test

Post #1348723

Robin Sasson

Posted Thursday, August 23, 2012 1:57 AM

Say Hey Kid

Group: General Forum Members
Last Login: Monday, February 18, 2013 6:17 AM
Points: 674, Visits: 472

Good article and clear explanation.

Had do refactor the INSERT statements as my organisation uses SQL 2005.

Exclamation

"Be brave. Take risks. Nothing can substitute experience." Exclamation

Post #1348910

« Prev Topic | Next Topic »

Permissions