MMartin1

  • Interests: Movies, Skating, S.Q.L. SERVER, Business Intelligence, Some Guitar.

SQLServerCentral Article

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 […]

3.77 (13)

You rated this post out of 5. Change rating

2021-05-19

10,559 reads

Blogs

What to Know about Power BI Theme Colors

By

Power BI reports have a theme that specifies the default colors, fonts, and visual...

A Global Team Meeting

By

The last few years at Redgate we’ve had the entire (or most) of the...

A New Word: sayfish

By

sayfish – n. a sincere emotion that seems to wither into mush as soon...

Read the latest Blogs

Forums

should i make as many datafiles for temdb as many cpus i have

By rajemessage 14195

hi, q1 As people said if u ghave GAM conention then u can go...

Script

By ramana3327

We have about 30 databases in server A.  All of them need to migrate...

Add alarms to database when a query, stored procedure, SSIS package hangs

By Lord Slaagh

Hello SSC, I am a SQL Server developer that has some DBA skills. I...

Visit the forum

Question of the Day

The Secondary Database Name in an AG

I am setting up a SQL Server 2022 Availability Group and I am ready to restore the database on the secondary. The primary database is named Finance. However, we also use this instance for QA and already have a database named Finance. How do I configure the AG to use a different database as the secondary?

See possible answers