Mistakes occasionally happen. Occasionally, you make some ill-judged 'refinements' to working code and now just wish you could rewind your tab back in time an hour and forget the whole sorry episode. Now and again, SSMS just conspires against you and crashes unexpectedly, and you lose all your currently open query tabs, some of which you hadn't saved. SQL History offers a useful safety net in the event of any of these unfortunate events.
As much as we tell people to use SCHEMABINDING and avoid SELECT *, there is still a wide range of reasons people do not. A well-documented problem with SELECT * in views, specifically, is that the system caches the metadata about the view from the time the view was created, not when the view is queried. If the underlying table later changes, the view doesn't reflect the updated schema without refreshing, altering, or recreating the view. Wouldn't it be great if you could stop worrying about that scenario and have the system automatically keep the metadata in sync?
Technology has always been a driving force in shaping our world, propelling us forward into new realms of innovation and progress. One of the most famous concepts in technology is Moore's Law, which suggests that the number of transistors on a microchip doubles approximately every two years, leading to exponential increases in computing power. In […]
This article looks at security mechanisms in the cloud that can help protect your data, with specific examples in AWS.
The loss of developer knowledge can be impactful for an organization. Steve notes that they should do more to retain their staff.
There are many great tutorials on syntax, performance, and keywords for invoking subqueries. However, I wish to discover a tip highlighting selected SQL subquery use cases. Please briefly describe three SQL subquery use case examples. For each use case, cover how a subquery interacts with outer queries and the T-SQL for implementing the use case. Review excerpts from each example to show the value of implementing the use case.
Too much data, especially for some data analysis isn't good for diversity of any product domain.
Over the past 25 years, I have answered a lot of programming questions in online forums, from co-workers, and from friends. It has been a while since I had been around forums, but I recently decided it was time to get back to what started me in the SQL community: answering questions. Not only is it complementary to my current job as Simple-Talk editor, it is really a great joy to be able to help other people with their problems. It is also educational to see the kinds of things other people are going through before you also go through them.
In 2023, connect, share & learn with like-minded peers, speakers, and industry leaders during the full week of data celebrations. Summit happens in person, from November 14th to 17th in Seattle. Check out the blog post to learn more.
This is a survey from us at dataplatformwit.com to understand why /how you, as a woman technologist are engaging with community. We ask that women in the data community please fill this out.
By Vinay Thakur
Continued thinking about my Journey blog where we have to look back at the...
By SQLPals
PowerShell Remoting for SQL DBAs: WinRM + SSH Guide (Updated 2026) ...
By Steve Jones
We’re coming back to New York, which is exciting for me. I love NYC....
Comments posted to this topic are about the item Identities and Sequences II
Comments posted to this topic are about the item Using PostgreSQL as a NoSQL...
Comments posted to this topic are about the item Is Your Time "Free"?
In thinking about the differences between the identity property and a sequence object, which of these two guarantees that there are consecutive numbers (according to the increment) inserted in a single table?
See possible answers