As you noted, doing row-by-row comparisson is not efficient at all. If you switch to a set based method you'll find things will run much quicker.

For your error handling, add...

What service pack are you running?

Try dropping and re-creating the index for starters.

Most of the methods suggested here will not work against a named instance. The suggestion of running "SELECT SERVERPROPERTY('SERVERNAME')" won't work because you need to have a server connection to...

As the DTS packages are stored as binary objects in SQL Server there is no way script out the details of the DTS packages using SQL Enterprise Manager.

Best solution would be to import the data into a staging table in SQL Server that has all fields defined as varchar. Then you can run multiple SQL statements to...

Why is this something that is NOT about SQL?

The creation of the error log files is something that is built into the application. So there not much chance of you...

Have you discussed the problem with MS Support?

Just because your edition isn't listed doesn't make it a "careless mistake". Maybe they were only able to reproduce it on Standard Edition...

Ok, I'm confused, why can't I assume that an ActiveX Script task within the package won't run?

Our DTS packages move from various developer workstations to a QA server, to a...

We do the local create/robocopy process on all our servers couple of them have backups in excess of 10gb and they get shifted around without a problem.

Peter: Yes good catch on the indexes. Forgot the reverse of my argument And good pointers on the recovery model and database growth.

MG:...

I didn't think Access had stored procedures

Is this an Access Data Project that connects to a SQL Server database?

Have you looked into using products like LiteSpeed?

Nice article. A little different than the technique I use but effective all the same.

My table includes the package id as well and holds all the global variables for...

SQL is notoriusly fickle when utilising network shares. It only takes the slightest of network hiccups to kill a backup job.

Better long-term solution is to create the backup on the local...

First setup your workflow as normal. Then for the BULK INSERT  task add a workflow ActiveX Script that changes the precedence constraints appropriately.

Here's a script I use to run a...