We accomplish this by using a form which captures the parameters and ends with an 'OK' button. The 'OK' button is an event which creates a SQL command string...

Jeffrey Williams (4/24/2009)

---

What edition are you installing? Is it x86 or x64? If x64 and Standard edition you might have some problems with that much memory being allocated...

Is this on an HP box? I have SQL Server 2005 Std 64-bit on a 16 GB dedicated server - it was getting hammered with swapping all of memory...

Unfortunately Standard Edition ignores the Lock Pages in Memory option (There's a KB reference - I don't have the number handy but do a search on member problems and you'll...

Kurt - I have also found that applying DTA recommendations on the occasional 'bad' query (runs exceptionally long on 2005 compared to 2000) will 'fix' the problem - and I totally agree...

You most likely have a DTS package with a name that the wizard doesn't like.

I kept getting this error until I found a package that had a space as the...

I'm pretty sure you would have some issues with SSIS packages that run in SQL Agent jobs - on 64-bit SQL Server you have to call the 32-bit dtexec if...

Here is the best single discussion of 64-bit, SSIS and Oracle connectivity that I have found....

http://stevemchugh.blogspot.com/2007/02/adventures-of-ssis-and-oracle-in-64bit.html

 

Similar experience - 6 minute query on SQL 2000 was running 29 minutes on SQL 2005 with much higher performance hardware.

Examined execution plan on 2000 and used hints on 2005...

To use the 32-bit dtexec within a SQL Agent job you need to use the Operating System (Cmd Exec) job step type - ahead of your command line "/DTS ...."...

If you're running 64-bit check this thread:

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=148&messageid=357285

There are several threads dealing with the workaround needed for SQL Agent to run jobs requiring OLEDB providers which do not have a...

You cannot run an SSIS task that gets data from Excel or Access as an SSIS package job step - there is no 64-bit OLEDB provider for Excel or Access...

To follow up on Scott's comment regarding 32-bit/64-bit - if you create packages that require 32-bit providers (Excel, Access) and are going to execute these packages as jobs via SQL...

I don't know that I fully agree/understand the problem with building SSIS packages and executing them as a SQL job on a 64-bit platform.

I wish there had been a disclaimer...

OK, seem to have resolved most issues with the 32-bit command line dtexec use (thanks laker_42!).

My template for the command line is:

C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\dtexec...