Re: SQL Server 2000 DTS Designer Components

Tom,

As an FYI, my main SQL Server 2005 servers are 64-bit as well and we run the 32-bit DTSRUN.EXE with no problem on those servers. I actually have not installed the DTS Designer on the servers directly, but install it on client machines of programmers and administrators who manage the DTS packages.

Having said that, I see that on my 64-bit server installation, the SQL Server Management Studio 2005, etc. are all x86 programs (32-bit) so the DTS Designer should work even there.

Regarding running DTS packages, once the legacy components are installed, my SQL Agent job steps are Operating System steps (not SQL Server Integration Services steps) and are in the form:

dtsrun /F \\Server\Path\MyPackage.dts /N NameOfPackage

From this you can see that we store the DTS packages in the file system,
rather than in the msdb tables. (This is to allow more than one person to manage the DTS package.) But it should work fine even with packages stored in msdb.

Anyway, they run just fine on 2005 and I would expect them to continue to do so on 2008.

RLF

"Tom Frost" <frosty@xxxxxxxxxxxxx> wrote in message news:68E92721-D12E-4FFE-85F9-ABB5F0208F7D@xxxxxxxxxxxxxxxx
One thing I neglected to mention, the environment is a win server2008 x64
enterprise..

thks

"Tom Frost" wrote:

I'm receiving the following messsage from a SQL 2008 Client when I attempt to
open a DTS package for editing from a registered SQL 2000 Server . I have
been unable to locate the SQL 2000 DTS Designer Components for SQL 2008, only
for SQL 2005 and they dont appear to work.

TITLE: Object Explorer
------------------------------

SQL Server 2000 DTS Designer components are required to edit DTS packages.
Install the special Web download, "SQL Server 2000 DTS Designer Components"
to use this feature. (Microsoft.SqlServer.DtsObjectExplorerUI)



.

Relevant Pages

  • RE: Recover SQL files & DST packages from server backup
    ... > after you install the OEM copy on the SBS box. ... If the DTS Packages are saved to SQL Server, they would be saved in the ... > sysdtspackages table in the SQL Server msdb database. ...
    (microsoft.public.windows.server.sbs)
  • RE: DTS Designer problems after upgrade to SQL Server 2008
    ... SQL Server 2000 DTS Designer components are required to edit DTS packages. ... "SQL Server 2000 DTS Designer Components" ... No resolution was achieved. ...
    (microsoft.public.sqlserver.dts)
  • Re: DTS Designer problems after upgrade to SQL Server 2008
    ... I think the same error occurred with SQL Server 2005, and there was a KB article on how to install the DTS components. ... I remember starting with downloading the DTS Designer components, and installing those, but I think there was another more obscure step. ...
    (microsoft.public.sqlserver.dts)
  • Re: Simple questions
    ... Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) ... option to create the destination table. ... can I use the DTS Designer package to preserve the ... autonumber in Access and, going forward, will be an identity column in SQL ...
    (microsoft.public.sqlserver.dts)
  • Re: Show only permitted database
    ... > DTS designer in EM is client side. ... > Jasper Smith (SQL Server MVP) ... >> Dennis. ...
    (microsoft.public.sqlserver.security)