Count distinct in Access with a subquery in the FROM clause, because Access SQL does not accept COUNT(DISTINCT). Includes NULL and multi-column cases.
SQL Server emergency? Email pinal@sqlauthority.com with URGENT in the subject line.
SQL SERVER – Identity Column is Difficult to Remove
The IDENTITY property is difficult to remove through a column alteration because SQL Server doesn’t support that operation. Existing values need protection.
Index Used for COUNT(*): SQL Server Scans the Narrowest One
The index used for COUNT(*) is the narrowest one that holds every row. See the pages, the scans and the reads that prove it in SQL Server.
Index Scans – Good or Bad? – SQL in Sixty Seconds #174
Index Scans – Good or Bad? Lots of people ask about this question and I have built a blog post on the topic – SQL SERVER – Index Scans are Not Always Bad.
SQL SERVER – Index Scans are Not Always Bad
Are Index Scans Bad? The answer No. Index Scans are Not Always Bad. This was in-depth discussed with my client during the Health Check.
Optimize for Ad Hoc Workloads – SQL in Sixty Seconds #173
Today we are going to discuss if we should keep Optimize for Ad Hoc Workloads true or false. Let us see a detailed video about it.
Unlock SQL Login Without Changing the Password
Unlock SQL login accounts without a new password: switch CHECK_POLICY off and on. See the lockout, the fix, and what to do when MUST_CHANGE blocks it.
SQL Server slow? Let's fix it together in about four hours.
In my Comprehensive Database Performance Health Check, you share your screen, I guide you, and we fix your biggest performance troublemakers. No passwords. No remote access.
You keep every script, and the know-how to fix it yourself next time.
Want your whole team to learn it?
My Practical Workshop has no PowerPoint, just live demos. My AI Enablement Workshop shows your team where AI saves hours, and where it quietly costs them.
Over 400 customers have worked with me this way, and not one shared a password. See all consulting options.