Viewing 15 posts - 7,231 through 7,245 (of 59,102 total)
I'm not sure what the equivalent in the language of SSIS is but I have to believe that you shouldn't need to resort to a C# component. Here's how I...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2020 at 4:08 pm
Now, my requirement is , I want to retain latest 2 backups and delete the remaining old backups. How can we implement it programmatically.
Just a reminder about something that...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2020 at 3:50 pm
In the future, please provide the data in a readily consumable format so that we can test the code we provide as an answer. See the first link in my...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2020 at 3:41 pm
There is no question that the trigger is adding time to the problem. When you do a join of a million rows between two logical tables that probably spilled to...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2020 at 2:07 pm
With all the reading and analysis' that I've been doing based on Paul Randal's Wait Stats articles, I come to the conclusion that the issue is an IO subsystem...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2020 at 1:40 pm
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
Viewing 15 posts - 7,231 through 7,245 (of 59,102 total)