Not without a fair amount of pain. It is the opinion of most developers that cosmetics like this are better served in whatever reporting application you are using as opposed to in T-SQL, as doing it that way in a set would hose up grouping/sorting.
For example, in SQL Server Reporting Services (SSRS) in the textbox for the product_id column the HideDuplicates property can be set to True, which would blank out all 'duplicates' beyond the first row.
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
Do you want 3 rows with blank in 2 and 3rd row for first column?
Jim Dettman (EE MVE)
<<For example, in SSIS in the textbox for the product_id column the HideDuplicates property can be set to True, which would blank out all 'duplicates' beyond the first row.>>
Same is true in the Access report writer, but not in a query.
Jim.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
Jim Horn
typo correction, in my original comment I had SSIS instead of SQL Server Reporting Services (SSRS). Corrected.
For example, in SQL Server Reporting Services (SSRS) in the textbox for the product_id column the HideDuplicates property can be set to True, which would blank out all 'duplicates' beyond the first row.