April 11, 2025 at 12:00 am
Comments posted to this topic are about the item Elements of the SQL Server Update Statement
Br. Kenneth Igiri
https://kennethigiri.com
All nations come to my light, all kings to the brightness of my rising
April 11, 2025 at 7:26 am
Another good use case is using a join to a record set to do an update. This could be either another table or a CTE. I see this often enough. Plus the syntax cuold be different across database sytems, as is the case between t-SQL and Redshift. So it would be good to offer this illustration as well.
----------------------------------------------------
April 11, 2025 at 5:01 pm
Gosh... SQL Server, MySQL, PostgreSQL, and (finally after decades of not) even Oracle has the ability to do JOINed updates. Consider resubmitting this article with that critical functionality so that it will get better marks.
Consider your references. To the uninitiated, they seem to have nothing to do with the UPDATE statement. Either make them "connect" with the article or chose better references... perhaps something like the documentation for UPDATE offered by MS.
Also, it almost seems that the purpose of the article is to do a lead in for the advertisement of a product to replace SSMS, especially since the information about the main subject, the UPDATE Statement, is so very lacking. If the article were a post, I'd be tempted to mark it as SPAM.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2025 at 3:34 am
It does seem strange to me that there is a link, unrelated to the article, for a paid product.
----------------------------------------------------
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply