2012-01-25 (first published: 2011-12-15)
1,181 reads
2012-01-25 (first published: 2011-12-15)
1,181 reads
2012-02-07 (first published: 2011-12-15)
1,032 reads
2010-02-15
15,005 reads
In this whitepaper, you will see the benefits of migrating your SQL Server 2000 Data Transformation Services (DTS) packages to Integration Services by using two proven methods. You will also see how you can run and manage your current DTS packages inside of the SQL Server 2005 and 2008 management tools.
2008-11-07
5,110 reads
An proposal about using simple server name resolution and INI files to make a DTS package portable.
2008-04-10
4,215 reads
Many of us still have SQL Server 2000 DTS packages running throughout our environment. New author Owais Bashir Ahmed brings us an interesting technique for moving those packages between servers that might come in handy as you continue to work on these packages in SQL Server 2000.
2007-10-09
6,239 reads
Migrate to SQL Server 2005 and maintain, edit and develop your data transformation services (DTS) packages using the SQL Server DTS Designer.
2007-07-05
4,915 reads
While SQL Server Integration Services is a huge improvement in the ETL capabilities of SQL Server, there are quite a few environments still using DTS in SQL Server 2000. Wayne Fillis brings us a method for implementing conditional logic in your packages.
2008-03-19 (first published: 2007-06-07)
10,257 reads
SQL Server 2005 includes an amazing ETL environment in Integration Services, but many DBAs will be using DTS and SQL Server
2000 for years to come. Jambu Krishnamurthy brings us a few handy examples of how you can customize your DTS environment.
2008-02-08 (first published: 2007-03-22)
17,626 reads
When loading a data warehouse, handling the ETL process of working with files can be problematic. Longtime DBA Janet Wong brings us an interesting solution that is flexible and efficient for quickly loading a number of files into a warehouse using DTS.
2007-12-31 (first published: 2007-01-23)
9,936 reads
Here’s a way to centralize management, rotate secrets conveniently without downtime, automate synchronization and...
This may or may not be helpful in the long term, but since I’m...
By Steve Jones
“I’m sick of hearing about Red Gate.” The first article in the book has...
Comments posted to this topic are about the item Dynamic T-SQL Script Parameterization Using...
I have read that the collation at the instance level cannot be changed. I...
hi our on prem STD implementation of SSAS currently occupies about 3.6 gig of...
In SQL Server 2022, I run this code:
CREATE SEQUENCE myseqtest START WITH 1 INCREMENT BY 1; GO CREATE TABLE NewMonthSales (SaleID INT , SecondID int , saleyear INT , salemonth TINYINT , currSales NUMERIC(10, 2)); GO INSERT dbo.NewMonthSales (SaleID, SecondID, saleyear, salemonth, currSales) SELECT NEXT VALUE FOR myseqtest , NEXT VALUE FOR myseqtest , ms.saleyear , ms.salemonth , ms.currMonthSales FROM dbo.MonthSales AS ms; GO SELECT * FROM dbo.NewMonthSales AS nmsAssume the dbo.MonthSales table exists. If I run this, what happens? See possible answers