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

My Social Media Rules

By

I developed these rules a while back, before COVID. I had a period of...

Why Use TRY_PARSE(): #SQLNewBlogger

By

Someone asked why I would use TRY_PARSE after I posted a question at SQL...

A Guatemalan's Guide to Drinking Coffee Properly

By

My mugI grew up surrounded by coffee farms in Guatemala and somehow spent most...

Read the latest Blogs

Forums

Partitioning a table with TEXTIMAGE_ON option

By Brandie Tarvin

I have a table that ends in ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]. I'm about to...

OUTER APPLY Fundamentals: Part 2

By Imran2629

Comments posted to this topic are about the item OUTER APPLY Fundamentals: Part 2

Building Great Software

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Building Great Software

Visit the forum

Question of the Day

The Range of Customers

I have this data in the OrderHeader table in a SQL Server 2025 database (ordered by CustomerID ASC):

orderid orderdate               customerid complete
3       2025-05-10 00:00:00.0002          1
21      2024-01-10 00:00:00.0003          1
15      2023-10-28 00:00:00.0004   1
13      2025-03-08 00:00:00.0006          1
11      2024-04-02 00:00:00.0007          1
If I run this query, how many rows are returned?
SELECT *
 from dbo.OrderHeader
 where customerid between 3 and '6'

See possible answers