Viewing 15 posts - 7,216 through 7,230 (of 59,072 total)
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
CF normally doesn't stand for Code First, it is rather a notation of a Cluster Fxxk, but then again that would be the same thing
😎
Heh... I'll remind you that...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2020 at 11:32 pm
Now I find out about things later and wonder why they did it that way.
We all know the reason, though, right? It's the same reason why we sit in...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2020 at 11:11 pm
EFCF is great if you want everything to be NVARCHAR(256) and even True/False columns to be NUMERIC(18,0). That's great for the economy, as well, because it keeps a raft of...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2020 at 3:39 pm
Hello All,
thank you all for your contributions.
The problem was resolved.
Two way street here... 😉 Please tell us what you did to resolve the problem.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2020 at 2:51 pm
I have to say that I'm loving the isolation (of course, I don't have kids at home and I don't like the reason for the isolation). Not much has changed...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2020 at 2:11 pm
Thanks you Jeff for your accurate post; I will keep your observations in mind and I will consider them in they more general meaning. At the moment I am...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2020 at 1:55 pm
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2020 at 1:41 pm
>> I have a table with 2 fields [sic] DocumentID and ArrivedDate. <<
You might want to actually read the standards for SQL. A field is a subset of a...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2020 at 8:55 pm
It's conditional counting. Sql is terrible at this.
To add to that,
I agree with Ken here that the application side is better suited for this.
Personally, I would refrain...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2020 at 5:39 pm
Viewing 15 posts - 7,216 through 7,230 (of 59,072 total)