I have an accumulating snapshot fact table that tracks the entry and exit of containers in a terminal.
The containers can entry and exit in 3 different ways, so i thought to create a specific dimension table that lists these 3 possible ways (train, vessel or truck).
Then i read this article wh...
We list all known (to us) wait types in the Waitopedia, although I can't find AWAITING_COMMAND in there nor on MSDN.
Which version are you using? You would gain most from also checking against the workload analysis
It would be nice if we could vote for "delete and convert to comment" and not only for "delete"
@AndriyM This part?: "You would gain most from also checking against the workload analysis" Hardly an answer but I guess we could see it as an attempt to answer,
This gives the distinct count(*) for A partitioned by B:
dense_rank() over (partition by B order by A)
+ dense_rank() over (partition by B order by A desc)
- 1
Based on the limited Info, here is an Example of what I think you want:
USE TempDb
Go
CREATE TABLE #t1 (c1 int)
GO
INSERT INTO #t1 VALUES(1)
INSERT INTO #t1 VALUES(2)
INSERT INTO #t1 VALUES(3)
INSERT INTO #t1 VALUES(4)
GO
CREATE TABLE #t2 (c1 int)
GO
INSERT INTO #t2 VALUES(1)
INSERT INTO #...
we have a lot of blocking issues right now in production and I'm considering using it. I've read the official docs and some posts, like the one from Brent about it. Just looking for real issues/problems or whatever from people who've done it.
I guess it depends on your application. We don't run into any real world issues, and every single recent Dynamics installation uses it without any real issues
However, I would have to add that the problems in our app are largely due to a design that was never intended to handle the concurrency Microsoft is trying to sell it for
aka not enough normalization, wrong indexing, wide varchar indexes and clustered keys
yeah but problem is some of these need to have 4 or 5 tables or more populated in a single trans
parent item, then child item, then child items of that, then potentially child items of THAT, then potentially children of THAT, and then update the parent of the parent
my main worry with RCSI is impact on business operations, i.e. we have a list of projects to start in a queue, and that record is updated when someone starts work
I don't want someone else to think they can start that record
also some of this stuff is why I am trying to hire another engineer
b/c I do not have days of my own time to allocate to it unfortunately
@JNK That's the biggest thing IMO. For most scenarios, RC -> RCSI is not that dramatic (assuming adequate *tempdb etc.) but apps that rely heavily on the blocking behaviour of default RC can be tricky. The READCOMMITTEDLOCK hint is useful.
the logic is pretty well modularized in the DB so I have probably 1 or 2 stored procedures that would need to check that and I believe we really just have one or two tables that it will be an issue in
I know that the majority of my issues are code/design related but I am looking into ways to buy a little more time on major refactorings
@JNK In my experience it's worked wonders, given you can mitigate the risks and keep an eye on tempdb size and throughput, and as Paul says and I've mentioned we have no triggers
My broad experience has been that RC -> RCSI changes have been less dramatic than feared in all cases, but it is definitely good to start out a bit scared by the change.
I recently posted a question here that garnered a couple nice answers. I selected the best one that worked and went on my merry way. Now, however, my requirements have changed slightly, but enough that the the answer doesn't quite fit.
Is it more appropriate to create another question, and mayb...
I have an accumulating snapshot fact table that tracks the entry and exit of containers in a terminal.
The containers can entry and exit in 3 different ways, so i thought to create a specific dimension table that lists these 3 possible ways (train, vessel or truck).
Then i read this article wh...
We list all known (to us) wait types in the Waitopedia, although I can't find AWAITING_COMMAND in there nor on MSDN.
Which version are you using? You would gain most from also checking against the workload analysis
This gives the distinct count(*) for A partitioned by B:
dense_rank() over (partition by B order by A)
+ dense_rank() over (partition by B order by A desc)
- 1
I recently posted a question here that garnered a couple nice answers. I selected the best one that worked and went on my merry way. Now, however, my requirements have changed slightly, but enough that the the answer doesn't quite fit.
Is it more appropriate to create another question, and mayb...
