Integration Services (SSIS)

SQLServerCentral Article

Upgrading SQL Server 2000 DTS Packages to SSIS

  • Article

If you're like Brian Knight, you probably have dozens if not hundreds of DTS packages running around that you're terrified to touch. SQL Server 2005 has some interesting methods to upgrade your packages to SSIS with minimal effort. This article shows you a few ways that you can use to upgrade and some of the drawbacks.

(14)

You rated this post out of 5. Change rating

2008-05-23 (first published: )

66,103 reads

Technical Article

SQL Server 2005 Integration Services, Part 2: Developing Custom Compon

  • Article

The first phase of Project REAL included the migration of existing SQL Server 2000 DTS packages to SQL Server 2005 Integration Services (SSIS) for a large electronic retailer. One source of information for the data warehouse was from TLog files, which contained data from point-of-sale cash registers in stores. TLog files store data in packed decimal format. To extract and transform this data into a format suitable for loading into the relational data warehouse tables, it was necessary to unpack and parse the files. To achieve this, custom pipeline components were implemented to read and transform the data by extending the SSIS object model. This paper discusses what we learned while implementing the pipeline components for extracting and parsing data from the TLog parser

2005-12-27

2,067 reads

Technical Article

SSIS Packages are Encrypted by Default

  • Article

By default, SSIS files in development are encypted to prevent an unauthorized person from seeing your SSIS package. The type of encyrption is seamless behind the scene and is at a workstation and user level. So, if you were to send a package that you're developing to another developer on your team, he would not be able to open it by default. This shows you how to fix this problem.

2005-12-20

1,683 reads

SQLServerCentral Article

An Elegant ETL Solution: Except for Lost Data

  • Article

An early adopter of SQL Server 2005 found some issues with Integration Services. And he shows how it was debugged and the issue solved. This is a great look at some of the helpful parts of Intration Services in solving problems as well as a few places it falls short.

You rated this post out of 5. Change rating

2005-12-02

5,844 reads

Blogs

Flyway Tips: AI Deployment Script Descriptions

By

With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...

A New Word: Fawtle

By

fawtle – n. a weird little flaw built into your partner that somehow only...

Post-quantum key exchange – Insurance policy for your packets

By

AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...

Read the latest Blogs

Forums

Where Your Value Separates You from Others

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Where Your Value Separates You...

Fixing the Error

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Fixing the Error

T-SQL in SQL Server 2025: Encoding Functions

By Steve Jones - SSC Editor

Comments posted to this topic are about the item T-SQL in SQL Server 2025:...

Visit the forum

Question of the Day

Fixing the Error

On SQL Server 2025, I have a database that has this collation: SQL_Latin1_General_CP1_CI_AS. I decide I want to run this code:

SELECT UNISTR('*3041*308A*304C*3068 and good night', '*') AS 'A Classic';
I get this error:Msg 9844, Level 16, State 4, Line 24 The char/varchar input type uses an unsupported collation. Only a UTF8 collation is supported with char/varchar input type in UNISTR function.What is the easiest way to fix this error?

See possible answers