There really is an abundance of documentation and tools to do MS SQL Server to MySQL migrations - likely there would be no need to re-invent the wheel. Exporting your database tables' data to CSV just to re-import it to MySQL seems like a rather bad idea since you are going to lose all metadata (data types, constraints, indexes, views, ...).
Look at this ...
You ave to use /!X /!C after the DTS command.
/!X ==> Do not run the package
/!C ==> copy the results to clipboard
To avoid this, you can create a SQL Agent Job and choose CmdExec as a step type with below commandline:
DTSRun /N"your package name" /S<servername> /E --- for trusted connection
DTSRun /N"Your package Name" /S<ServerName>...
You can achieve this without using Foreach enumerator, just use one data flow task to achieve this.
Building the Package
First of all, add a Data Flow Task to the control Flow
1. OLEDB Sources
In the DataFlow task add an OLEDB Source that Read from Orders Table (the same command used in the Execute SQL Task (first step in your question)
Select * FROM ...
When a SQL Server agent job is run it is run on the SQL Server machine not on your workstation.
It sounds like you don't have the drivers setup correctly on the SQL Server.
Keep in mind that if you are using a 64bit machine you'll need 64bit drivers and god only knows how DTS will handle 64bit stuff.
DTSInstaller.exe consumes a file called with an extension of SSISDeploymentManifest
The contents of it look like
Per all the references I can find (most notably Upgrade Integration Services Packages on MS TechNet, and this StackOverflow answer), the options are:
Use the tools available with SQL Server 2005 or 2008 to convert the DTS package to an SSIS package; then, upgrade the SSIS package with SSDT; or
Rewrite the package with SSDT, for your current SQL Server ...
Could you share the linked object name along with the query?
Sometimes the problem is on the FROM part. There are a lot of situations where you can get this error, and many of them are covered on StackOverflow. However, one case which might especially be encountered on shared servers is simply that the database name has a period (dot) in it. For example, if ...
Ok. I was able to find the root cause (hopefully) and circumvent it. Most likely the reason was type mismatch 'join' was because ACCT_ID was NULL in the source table.
The below worked fine:
IF NOT isNULL(DTSSource("ACCT_ID"))
varamt = Lookup ("Lookup_tbl1",
Does a SQL Server Job always run on the server or will it run in the context of the local machine, similar to a DTS package run from Enterprise Manager on the user's machine?
For TSQL, Agent uses its own login (Windows authentication), and then uses EXECUTE AS LOGIN = 'n' command to simulate you. For other job step types, Agent uses Proxy and Credentials. ...
You could use Oracle Data Integrator for this. See Oracle Data Integrator documentation for a good starting point. If you want you can build this yourself. Change Data Capture can be used. Make a change table in Oracle that receives the change records from the Oracle source and implement the change records to the sybase destination tables.