We have SQL Server 2000 databases residing on one server, for reference I am
calling them DB1 and DB2. DB1 contains the main data,

DB2 contains data about the most recent changes to DB1, The key, table ID,
timestamp, and what action (insert, update, delete) occurred to DB1 is stored
in DB2.

We have a MySQL database connected to a live web server.

Our plan is to schedule a DTS package to update the MySQL database. The DTS
package uses a Data Driven Driven query task between the two SQL Server 2000
databases to populate the source that are sent to the bound MySQL database
using insert and update parameter queries.

My question is that is there a better way to do this?

Also, we are planning to schedule this package to run every 15 minutes, and
have a send email task in case of failure. Is there a way to stop the
scheduler automatically in case of a failure so that when there are multiple
failures and the recipient is busy they do not send out multiple emails?

You didn't say how you were updateing the MySQL database, so I assume you
are doing it outside of your DTS package. I haven't worked with MySQL much
but I believe you can have a step in your DTS package that will update the
tables on the MySQL database. To do this you will need the correct ODBC
drivers, etc. I'd google for 'MySQL DTS' to see what I could find there.
Having everything in one neat package makes more sense to me than multiple
jobs on multiple servers.

The other part of your problem is disableing the job schedule. The msdb
database has a number of useful stored procedure, like sp_Help_Job,
sp_Stop_Job, sp_Delete_Job, etc. Take a look at those & see if they help.
Make sure you are running as the correct user, so that you can get to these
stored procedures!


"MTsang987" wrote: