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,300 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,807 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,049 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,672 reads

Blogs

Learning from Mistakes: T-SQL Tuesday #194

By

We’re a week late, once again my fault. I was still coming out of...

Stupid Things I Did With AI: ASCII Art

By

I ran across this article recently (https://www.gatesnotes.com/meet-bill/source-code/reader/microsoft-original-source-code) and it has a great opening piece...

Simple Talks Podcasting in 2026

By

I’m in the UK today, having arrived this morning in London. Hopefully, by this...

Read the latest Blogs

Forums

Learning From Breakage

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Learning From Breakage

Python in Action to Auto-Generate an Optimized PostgreSQL Index Strategy

By sabyda

Comments posted to this topic are about the item Python in Action to Auto-Generate...

Adding and Dropping Columns I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Adding and Dropping Columns I

Visit the forum

Question of the Day

Adding and Dropping Columns I

I have this table in my SQL Server 2022 database:

CREATE TABLE [dbo].[CityList]
(
[CityNameID] [int] NOT NULL IDENTITY(1, 1),
[CityName] [varchar] (30) COLLATE SQL_Latin1_General_CP1_CI_AS NULL
) ON [PRIMARY]
GO
I decide to add two new columns for the StateProvince and Country. What code should I use?

See possible answers