Being a bit pedantic, but I've read that article before and some of the arguments against also apply to the default READ COMMITTED isolation level. In either case you can...

You'll want to take a look at isolation levels. If dirty reads shouldn't be allowed (I agree with you that you need to be extremely cautious with them), but locks...

I'm no expert on partitioning, but there's a difference between a clustered index and a Primary Key. I don't believe you can use DROP_EXISTING to drop a clustered PK (which...

Nope. You have to drop and recreate it (same if you want to change the definition of a computed column).

If you need to maintain the column order (which you...

It'll display once for every distinct group of your group by clause as with any other GROUP BY...

In the row that you believe is duplicated, one or more of the...

You would have to add a dummy ROW_NUMBER type column and pivot this (either through PIVOT or a "crosstab").

Would be interesting to get some understanding of why you need...

Your requirement isn't very clear from your sample data (it would help if you posted DDL, insert statements etc.) Are you saying you need an unlimited amount of columns (one...

Duplicate:

http://www.sqlservercentral.com/Forums/Topic1174014-391-1.aspx

mustapha-721538 (9/12/2011)

---

Thank you for this solution.

One issue is solved now I´m displaying 0 instead of NULL in all the columns except the total column it still displays NULL when at...

You just need to wrap ISNULL's around your final SELECT - if there are no rows that match the PIVOT criteria, it'll resolve to NULL:

SELECT MaingroupNo, MainGroupName, ArticleNo, Name,

ISNULL([1],0) AS...

Why do your variables already have values that you want to NULL? Surely they should be NULL before the assignment.

Whilst using an aggregate function will likely work for numeric data...

I think you're missing the OP's point.

The reason for the problem is that the set command is explicitly setting the variable to a result set that evaluates to NULL...

Yep, definitely happens on a couple of different BIDS environments

Ninja's_RGR'us (9/9/2011)

---

I think this closes the debate. Th eproblem will self-correct in further releases :

See the semi-column after begin tran

BEGIN TRAN;

--no EXECUTE

sp_who2

ROLLBACK

/*

Msg 102, Level 15, State 1, Line 4

Incorrect...

I believe it's accurate, but not transactionally consistent, so you could potentially see counts that were later rolled back.

In reality, I don't see many cases where that would present...