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,810 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,054 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

SQL Server Security – TDE Encryption

By

Transparent Data Encryption(TDE): TDE was initially introduced in SQL Server 2008 Enterprise Edition; this...

A Las Vegas Break

By

Only a little break for me. I’m actually heading to Las Vegas today for ...

Finding Balance: Things Will Come Up

By

I have a presentation on finding balance in your career that got quite a...

Read the latest Blogs

Forums

The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI

By Terry Jago

Comments posted to this topic are about the item The day-to-day pressures of a...

Migrate SSRS Reports to PowerBI Report Server in SQL Server 2025

By Deepam Ghosh

Comments posted to this topic are about the item Migrate SSRS Reports to PowerBI...

Identities and Sequences III

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Identities and Sequences III

Visit the forum

Question of the Day

Identities and Sequences III

When thinking of the Identity property for auto incrementing columns and sequences for the same action, which can be used with the BIGINT data type?

See possible answers