External Article

A Few Cool Things You Can Identify Using the Default Trace

If you are running an instance of SQL Server 2005 and above then most likely that instance is running the default trace. This default trace is a canned Profiler server side trace that automatically starts up when SQL Server starts. In this article Greg Larsen explains more about the default trace and shows you how to glean some event information from the trace files created by this background trace process.

External Article

Using Friendly Names for SQL Servers via DNS

Wouldn't it be great if your HR folks only had to put in HR-SQL.mydomain.com for the database connection in their reports? They wouldn't have to remember it was on server Nile and they certainly wouldn't have to change their reports if you migrated their database from the Nile server to the server named Danube. In DNS there are two easy ways to do this.

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