2025-03-03
487 reads
MMartin1
- Interests: Movies, Skating, S.Q.L. SERVER, Business Intelligence, Some Guitar.
Hidden Pitfalls with INNER JOIN and NOT IN Operators
I want to show you how two common operators can deceive you into believing you have constructed a proper SQL statement for your solution. We may want to filter results in a table by using using a IN/NOT IN or a INNER JOIN/LEFT JOIN to another table. There are a couple of hidden dangers here […]
2021-05-19
11,898 reads
2016-11-01
1,302 reads
2016-01-13
1,497 reads
Blogs
Setting Up a Mac for Data Engineering and AI Work
If you work with data pipelines, SQL, notebooks, or machine learning models, a Mac...
Want to look at cloud reporting but not sure what the costs will be?
By ChrisJenkins
Have you been thinking about migrating your reporting to Microsoft Fabric or Snowflake but...
The Joyful Craftsmen and the Revolt BI join forces
The Joyful Craftsmen has become the new owner of Revolt BI. The merger creates...
Forums
SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Concurrency and Baseline Control: Level 5 of the Stairway to Reliable Database Deployments
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Spending Time in the Office
Comments posted to this topic are about the item Spending Time in the Office
Question of the Day
Multiple Values Inserted
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers