2012-01-25 (first published: 2011-12-15)
1,189 reads
2012-01-25 (first published: 2011-12-15)
1,189 reads
2012-02-07 (first published: 2011-12-15)
1,045 reads
2010-02-15
15,077 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,222 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,276 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,294 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,646 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,955 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers