Articles

SQLServerCentral Article

Preventing Identity Theft Using SQL Server

Solving business problems is an interesting problem for most application developers. Usually the issues are handled in application code, but there are some places where SQL Server can be used to help. Yaroslav Pentsarskyy brings us a creative use of SQL Server functionality to prevent identity theft.

You rated this post out of 5. Change rating

2006-09-20

6,335 reads

SQLServerCentral Article

Beauty is in the Eye of the Beholder

Is dynamic SQL good or bad? We've had lots of arguments over the years in the forums and articles on both sides of the coin, though with most of the opinions being that dynamic SQL is bad. Stephen Hirsch brings us his own view that beauty is in the eye of the beholder.

You rated this post out of 5. Change rating

2006-09-19

5,829 reads

Blogs

Advice I Like: Respect

By

“Don’t aim to have others like you; aim to have them respect you.” –...

Blue Sky Programming – The Optimism Trap

By

Many years ago, before I joined Oracle, I was working on a major modernisation...

Setting Up a Mac for Data Engineering and AI Work

By

If you work with data pipelines, SQL, notebooks, or machine learning models, a Mac...

Read the latest Blogs

Forums

SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About

By Terry Jago

Comments posted to this topic are about the item SQL Art, Part 4: Happy...

Alamat kantor BCA KCP Galuh Mas Telp:0817866887

By Layanan_BCA_24jam

WhatsApp:0817-866-887 Area Street Festival, Ruko No 1 & 1A, CBD, Jl. Galuh Mas Raya,...

Is Fabric a Reliable Service or a Ripped Resource?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Is Fabric a Reliable Service...

Visit the forum

Question of the Day

BIT_COUNT I

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

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

See possible answers