hey guys, at a pretty basic level, i have a stored proc along the lines of this. is there any risk of the recursive CTE creating a deadlock, thus requiring the joins to be done with no lock or should i just leave it for now and if it ever occurs then add the nolocks?
While I am rather pessimistic about whether anyone will manage to clean out the Augias' stable of fiefdoms and overall dysfunctional culture that Stack Overflow seems to have become on the inside.... this is definitely a breath of fresh air and the first corporate communication in years that spar...
I think it's funny that you consider the nasty people alt right - I consider the nasty people ctrl-left. I agree with you that there are definitely a lot of nasties though
@WhatsThePoint consider implementing optimistic concurrency via the database-level setting for READ_COMMITTED_SNAPSHOT or snapshot isolation at the transaction level - read about it here and here
@PaulWhite9 Interesting that other folks are focusing on the culture and 'personal fiefdoms.' Every time I've seen dogma deeply embedded in an organisational culture it always arises from somebody using it as a rhetorical device to label and discredit people they view as a threat. I'll still argue that over-the-top PC culture is a red herring and the root cause is somebody's empire building. They just happen to have latched onto this as a rhetorical device.
"This self-ordering behavior occurs naturally in the IT world because it is populated by people skilled in creative analysis and ordered reasoning. Doctors are a close parallel. " LOL
Empire Building 101: An empire builder is someone who builds up a network of soft influence within an organisation, usually for self-serving ends. Their objective is to control events surrounding their personal fiefdom and they will interfere with other departments projects, attempt to undermine or obstruct their work or discredit other parties. It's regarded as a major sin in management because of how destructive it can be.
Empire builders can only function when their management turns a blind eye or is otherwise unable to see through their bullshit. Dollars to donuts, the management problems at SE are down to a serious case of empire building.
Find the empire builder by seeing who everybody is fighting with or afraid of. There are consultancy firms that do this sort of thing. Replace the empire builder and replace their line management. Make sure the replacements have a good bullshit detector as you will need to root out the rot they've recruited into the organisation.
A's hire A's. B's hire C's. Joel. You've been preaching it for 15 years. Now practice it.
The SJW stuff is all a red herring. This is entirely about somebody playing toxic power games.
Empire builders are always highly manipulative; that's how they operate. Chances are that the source of the problem is someone that the SE board trusts.
Forget the SJWs. They are a red herring.
The SJW dogma is merely a convenient rhetorical tool that the originator is using as a political bludgeon to attack their rivals. They may or may not even believe in it. They've also managed to dog-whistle up some groups of supporters to attack on their behalf - notice that the originating party hasn't actually come forward. The empire builder's MO is to get others to do their dirty work.
now they need to follow through and "replace their line management. Make sure the replacements have a good bullshit detector as you will need to root out the rot they've recruited into the organisation."
@James I'm pretty sure it wouldn't be hard for someone inside the organisation to figure it out but they're not saying.
Contract work tends to find one being hired by dysfunctional organisations on a semi-regular basis. I've seen three organisations with a serious empire building problem now. It's always one particular individual reporting to incompetent line management.
Weaponised dogma was used in two of those organisations. Empire builders also like to position themselves as confidantes of their management and wage wars against people they consider a threat. The spate of mods leaving smells a lot like a political purge to get rid of potential threats.
The dogma doesn't really matter. I saw one place where somebody managed to use Agile theory as a rhetorical tool.
The inflexibility of the dogma is what makes this smell like empire building. It suggests that it's being used as a rhetorical device rather than as a symptom of a genuinely held belief system.
P.S. The fact that SE is still putting out transparent propaganda is a pretty strong indicator that the problem hasn't been rectified; the source of the toxicity is still working there.
@ConcernedOfTunbridgeWells that sounds nice. i didnt really eat much of the deep-fried stuff in korea, but i do love kimchi - it takes a bit for the gut to get used to a steady stream of it, though
Fair enough, I need the where clause for getting the children given a category. It's part of an application where a user has access to certain categories, and all children of those categories
@billinkc Sorry I'm not sure which type of hierachy. Here's an example: A Miller, Heiniken are both beer, beer is alcohol, alcohol is liquid. Another ex: A is B, B is C, B is also apart of D
PeopleSoft and some other system take that approach. Can make it easier to keep your structure in tact as things move about (if that's a concern for the system)
I'm working on an etl task that takes tables from one schema (with no constraints) and inserts them into the same tables (plus constraints).
I don't want to type out a bazillion insert statements, so I wrote some dynamic sql that looks like this:
declare @table varchar(255),
@stgtable varchar(2...
How much of this may just be the particular server resources being low? Because this is only happening on the automated test runs of the exact same data/schema/procs on SQL Server 2016 and not SQL Server 2012. It is a fairly large set of unions of the results of many table-valued functions. It just a got a little more complex than it was yesterday.
"The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify…
SQL 2016 is generally worse, has lower limits than 2012 or is there something with this instance?
I only test locally on 2012 so I don't use language features past that version and obviously my local 2012 instance is fine. And the 2012 instance used by Team City to install and test the database is fine. The 2016 might be different. I'll have to install and test against a local 2016 and see if it works, then it would be something up with that other 2016 instance.
Or I could refactor the code to simplify it. None of this code is in the product, this version is in code freeze, it's all the test harnesses that test runs that I am improving and expanding to test more things and.
This isn't even in the test runs themselves, it's the building of the test run results document, so it's just tons of nested and unioned ITVFs, many of them code-gened to cover all the categories of test cases.