Viewing 15 posts - 7,231 through 7,245 (of 59,091 total)
How many columns are actually in the table we're talking about?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2020 at 1:47 am
I could be wrong but I'm pretty sure that's not what the OP is talking about. I believe he's talking about the front-end Developers creating the tables on the fly...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2020 at 12:11 am
That's freaking amazing. It's awesome to see real in depth analysis. Thank you for doing this.
Shifting gears a bit, since the Nested Sets method has most of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2020 at 11:59 pm
Ok, so I commented the columns we spoke of out and ran your code. I had to make minor repairs because I already had an Employee table with a PK...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2020 at 9:42 pm
It's not going to work against the million node test table because of the following code...
sum(iif(Hlevel=1,1,0)) lvl_1_count,
sum(iif(Hlevel=2,1,0)) lvl_2_count,
sum(iif(Hlevel=3,1,0)) lvl_3_count,
sum(iif(Hlevel=4,1,0))...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2020 at 2:57 am
You're misunderstanding CI and ML.
Maybe but I don't believe so. For example, you wrote...
CI is designed to catch these things. Developers do not magically write better code with...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2020 at 8:20 pm
>> Now it is you that is putting words in my mouth. ?? That's not what I said. <<
No I think you misread, this principle is from Brent Ozar....
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2020 at 8:10 pm
Wow... just freakin' WOW!!! I thought that continuous integrationist and deployment was supposed to prevent this type of thing.
The first paragraph (quoted below) is what is really shocking to...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2020 at 5:38 pm
I completely agree with Celko.
Heh... being stuck with character-based identifiers due to a legacy system is one thing. Arbitrarily saying that all identifiers should be character-based because they're not...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2020 at 4:32 pm
Heh... I've got just one more thing to add when it comes to the transfer of large volumes of properly formed tabular data...

--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2020 at 4:15 pm
Imo expressing the recursive "downlines" or "sort path" as nested json makes the information much more usefully accessible. You can check out an example at:
Can you use...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2020 at 4:05 pm
I've written an entire book on various methods for modeling treason hierarchies and SQL. Get a copy and see which technique is most appropriate for your particular situation.
I'll add...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2020 at 4:02 pm
Imo expressing the recursive "downlines" or "sort path" as nested json makes the information much more usefully accessible. You can check out an example at:
Can you use the "Sort...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2020 at 3:35 pm
p.s.
If you want to seem some "Black Arts" magic with these kinds of Adjacency List hierarchies and learn about Nested Sets and other cool things, check out the following two...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2020 at 1:17 am
It can be done in using a single recursive cte. You just need to pass the first found roots to the rest of the hierarchy. We might as well sort...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2020 at 1:03 am
Viewing 15 posts - 7,231 through 7,245 (of 59,091 total)