External Article

Using SQL Server's Default Trace to Identify Autogrow Events in tempdb

We all know that you should try to size tempdb appropriately, so it doesn’t need to autogrow shortly after starting up SQL Server. It isn’t always easy to do this. Therefore, when you first implement a new server and/or add new databases you should monitor the autogrowth events on tempdb. By monitoring the autogrowth events you can easily determine if you have sized tempdb appropriately.

External Article

Principles of Data Protection

Protecting data in SQL Server is not as simple as setting a few properties. While there are great security features in SQL Server, such as Transparent Data Encryption, production data may end up in places throughout the organization. In this article, Brian Kelley talks about the best ways to secure data using the concept of least privilege.

Blogs

KDA: Echoes of Deception - Case 6

By

A cryptic message, a book cipher hidden in art provenance records, and a trail...

Capturing My Own Metrics: #SQLNewBlogger

By

A customer was trying to compare two tables and capture a state as a...

Red Flags in Your Query (T-SQL Tuesday #200)

By

When I'm looking at a query, I bet it's bad if I see... a...

Read the latest Blogs

Forums

BIT_COUNT II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item BIT_COUNT II

I Can't Make You Learn

By Steve Jones - SSC Editor

Comments posted to this topic are about the item I Can't Make You Learn

Why Your SQL Permissions Disappeared

By deepeshdhake

Comments posted to this topic are about the item Why Your SQL Permissions Disappeared

Visit the forum

Question of the Day

BIT_COUNT II

In SQL Server 2025, I have a table (dbo.UserPermission) that contains this data:

UserID  UserPermissions
15
23
37
4       NULL
What is returned when I run this code:
select bit_count(UserPermissions) as PermissionCount
from dbo.UserPermission
where UserID = 4;

See possible answers