Re: Scheduling DTS Packages on 64-bit SQL Server

From: Darren Green (darren.green_at_reply-to-newsgroup-sqldts.com)
Date: 10/21/04 

Date: Thu, 21 Oct 2004 18:15:53 +0100

My understanding is that DTS components are not available for 64-bit SQL
Server.

SP3 clients, because they are aware of this limitation they will not let
schedule a package to run on the 64-bit server as it knows this will fail.
You need to execute your DTS packages on a 32-bit machine, but I don't think
you need a new copy of SQL Server as DTS can be redistributed, or just
install the 32-bit tools to install DTS on the machine. Providing you
interact with a large SQL system such as the 64-bit box and the 32-bit box
has CAL you should be licenced, but I strongly suggest you clarify the
licensing aspect with your local MS licensing team.

Technically it is no problem to run DTS on any 32-bit machine, with or
without the full SQL Server engine on, you just need the DTS components
installed, which are client side tools. 

-- 
Darren Green
http://www.sqldts.com
"BSCG" <BSCG@discussions.microsoft.com> wrote in message
news:62AC1578-8E21-4844-BF42-4285FB0F9762@microsoft.com...
> I found the following comment on Microsoft's website in regards to
scheduling
> a DTS package on a 64-bit SQL Server installation. My question is, do I
need
> to buy a 32-bit copy of SQL Server to store my packages on to be able to
> schedule them? Currently, I have a 32-bit client installed on one machine,
> which is Service Pack 3a, and the 64-bit version of SQL Server 2000
installed
> on another machine. I have been saving my packages on the 64-bit SQL
Server.
>
> "If the client installed SQL Server 2000 Service Pack 3 (SP3), the option
to
> schedule the package in SQL Server Enterprise Manager is disabled. If you
run
> the DTS Import/Export Wizard and you decide to save and schedule the
package,
> you receive an error message for the Schedule Package step. If you
> double-click the Schedule Package step, you receive the following error
> message:
> 'Cannot schedule a package on a 64-bit SQL Server'If the client is running
> SQL Server 2000 SP2 or earlier, the client can schedule the package by
using
> SQL Server Enterprise Manager or the DTS Import/Export Wizard. However,
the
> package is not successful when it runs as a scheduled job because of the
> missing DTS components."
>

Relevant Pages

  • Re: DTS job error
    ... the DTS schedule package functionality - you right click on ... the package on select Schedule Package. ... DTSRUN /~Zxxxxxxxxxxxx. ...
    (microsoft.public.sqlserver.server)
  • Re: DTSRun and Batch file
    ... >> install the DTS DLLs on the local machine. ... So the DTS package is running ... >> user to start a SQL Agent Job that runs the package. ... Darren Green (SQL Server MVP) ...
    (microsoft.public.sqlserver.dts)
  • Re: Error when running SQL 2000 dts Package in SQL Server 2005
    ... Lotus SQL Driver works fine. ... created a package in SQL 2000 and trying to call it in SQL 2005'S Legacy Data ... I am able to create a new table using this DTS ... OK so if this fails when you use the package in an Execute DTS 2000 Package ...
    (microsoft.public.sqlserver.dts)
  • RE: Sheduling DTS-Packages in SQL2005
    ... If you have downloaded and installed the SQL 2005 Legacy Components (should ... also be on the install medial) you should be able to manage, edit, and run ... To schedule the package, create a stored procdure wrapper that executes the ... T-SQL syntax for executing DTS.) ...
    (microsoft.public.sqlserver.dts)
  • Error invoking a DTS package remotely
    ... I ran into a problem invoking a DTS package from a different machine. ... invoke the package from another machine with only sql 7 on it. ...
    (microsoft.public.sqlserver.dts)
Loading