Viewing 15 posts - 7,201 through 7,215 (of 59,072 total)
The trigger is already in place and I can't just change the logic of inserting the deleted records when We already started inserting the inserted records.
The Diff is necessary...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2020 at 1:38 pm
I'll have to disagree with the stance you took (or at least the stance it looks like you took, I could be wrong) on "matching code". I'm not talking about...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2020 at 1:35 pm
Unfortunately, the actual table has 200 columns and I can't change the structure 🙁
But regardless of the number of columns, I'm able to reproduce the issue with the example...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2020 at 1:27 pm
One of the problem with the function is this bit of code...
(select * from inner_recur_cte for json path, root('downlines')) json_downlines
from
inner_recur_cte;A lot of people...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2020 at 12:34 pm
Hi Jeff Thanks for the article, very good and functional, as I understand every time that an employee changes parentId or there is a new one in the adjacent...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2020 at 12:13 pm
If you'd like to short-sheet Phil's good solution a bit, try this...
DECLARE @Day TINYINT =...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2020 at 3:27 am
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
Viewing 15 posts - 7,201 through 7,215 (of 59,072 total)