External Article

Creating SSIS Package Templates for Reusability

We often need to create similar SSIS packages which contain some common components such as connection managers, data flow components, log providers, event handlers, etc... So do we really need to create a package from scratch each time and add all these commonly used components in each package again and again. Is it possible to create a SSIS package with a basic structure/workflow and common components which can be used as template to create subsequent packages?

Blogs

Advice I Like: Respect

By

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

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...

Want to look at cloud reporting but not sure what the costs will be?

By

Have you been thinking about migrating your reporting to Microsoft Fabric or Snowflake but...

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...

locking down agent for new user on our dev machine

By stan

hi , a new user wants to be able to add sql agent jobs...

SQL Server Enum Implementation: A Single-Row View Strategy for Avoiding Magic Values

By Ivica Borscak

Comments posted to this topic are about the item SQL Server Enum Implementation: A...

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