Viewing 15 posts - 316 through 330 (of 59,063 total)
Bumping the post so that the post above shows up on the next page. This has been a long standing fault on this forum. I sure hope the get around...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2024 at 8:19 pm
If you look at the column headers of the file and compare them to the table, they don't match. We can't see your package to know what the mapping is. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 7, 2024 at 2:35 pm
To be honest, you're probably wasting your time doing traditional index maintenance. Worse yet, you could actually be perpetuating fragmentation if you're using REORGANIZE.
With the thought that I named the...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 7, 2024 at 2:03 am
If YOUR data center isn't "on the cloud", the On-Prem shouldn't be too different. Normally, "on-prem" is another way of saying that the "data center" is not only owned by...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 7, 2024 at 1:51 am
TBH... I'm deathly afraid of any changes or "improvements" that MS makes any more. The huge slowdown that started with the new cardinality estimator in 2016 was the first big...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2024 at 11:42 pm
I concur with the error found by Jeff Williams. I also concur with the OUTER APPLY method being faster. With the correct index, it's actually twice as fast as the...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2024 at 11:15 pm
Since the author of that article hasn't answered the latest question there in over 4 years, why not just try it and see? Then, you can answer poor Jose's question...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2024 at 12:49 am
To be sure, that's not "SQL Server". There's no such thing as SQL Server 20.2. What you're seeing is SQL Server Management Studio, which is also known as "SSMS". That's...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2024 at 12:33 am
Jeff, This works perfectly. The LEFT JOIN did the trick. I'm investigating this as part of my quest for knowledge. Thanks!
Thank you for the feedback!
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2024 at 9:48 pm
To follow up on Eddie Wuerch's good post, it's an old but powerful bit of ancient code known as a CROSSTAB. You can get a good introduction to them in...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2024 at 12:56 am
I'm not a ninja at it but you could try it in a "Maintenance Plan". To execute a proc, you would use an execute SQL block. You could have the...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2024 at 4:13 am
Here's another method. I got this idea for Piet Linden's post above. We could work on the dates as he suggested because your latest data has overlapping date ranges but...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2024 at 5:09 am
Thanks Jeff, that worked well.
Can I ask you to explain how it works, as reading it does nto make a lot of sense.
Kind regards.
Sure...
If we look at the original...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2024 at 4:01 am
I am still evaluating how to apply this to an existing table..
And there's the rub. Please provide 5 to 10 rows of readily consumable data for use to operate...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2024 at 1:42 am
Alan... you might want to explain what the bernieML.samd. stuff is.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2024 at 1:16 am
Viewing 15 posts - 316 through 330 (of 59,063 total)