Articles

SQLServerCentral Article

More Portable DTS Packages

There have been a few articles over time on how you can build DTS packages in SQL Server 2000 that are easily moved from one server to another. New author Tito David brings us another technique that not only migrates packages easily between servers, but between your development and production environments.

You rated this post out of 5. Change rating

2005-04-07

9,302 reads

Technical Article

SQL Server 2005 Editions and Integration Services

The SQL Server 2005 product family has now been announced, so with four editions available, what does this mean for SQL Server Integration Services? Starting from the bottom we have the free edition known as Express, and the entry level Workgroup edition, and neither include the full IS product. They have the Import/Export capabilities, but nothing more, so for simple loading and extraction of data this should suffice, but you will not be able to build packages.

2005-04-07

4,009 reads

SQLServerCentral Article

BDS SQL Digger 2.0 Released

Have you ever needed to find something in a stored procedure or function and found yourself trying to wade through syscomments? Ever want to know which views reference a table, but you don't trust sysdepends? BDS has released SQL Digger 2.0, a utility designed to help you search through your schema and code to find what you need.

(1)

You rated this post out of 5. Change rating

2005-04-05

3,808 reads

SQLServerCentral Article

Flexible DTS Packages with Perl

SQL Server 2000 DTS was a revolutionary programming environment, but one that was not without a few quirks. As often found with many Microsoft products, there were sections in your packages where things were hard coded, making them less flexible. New author Jeremy Brown brings us a look at how you can build extremely flexible packages using Perl.

You rated this post out of 5. Change rating

2005-04-05

11,053 reads

SQLServerCentral Article

Know Your Data

Or at least the types of your data. New author Roy Carlson was working in SQL Server 2000 to calculate some values based on row counts, sales amounts, etc. and discovered some interesting results. Without his sharp eye, a number of individuals would have been upset by the resulting lack of commissions, as may some of your clients. Read about some potential problems in your calculations if you are not careful with your data types.

You rated this post out of 5. Change rating

2005-04-04

6,673 reads

Blogs

Shifting Mindsets: Why FinOps is Essential for Cloud Efficiency

By

As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...

March 2026 SQL Server Security Updates

By

On Patch Tuesday, in addition to OS and Office security patches, Microsoft also released...

How Fabric Mirroring Transformed with SQL Server 2025

By

When mirroring was first released for Azure SQL Database, it used Change Data Capture...

Read the latest Blogs

Forums

Multiple Deployment Processes

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Multiple Deployment Processes

How to Use sqlpackage to Detect Schema Drift Between Azure SQL Databases

By Kunal Rathi

Comments posted to this topic are about the item How to Use sqlpackage to...

Upgrading Admin Queries

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Upgrading Admin Queries

Visit the forum

Question of the Day

Upgrading Admin Queries

I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?  

See possible answers