Question about memory usage when running 32 bit DTEXEC.exe

  • I am running the 32 bit version of dtexec.exe (from the program files (x86) directory) on a 64 bit server that has 8 GB of memory.

    Is there any type of memory restriction running the 32 bit version? Is there any performance issue in this setup, regarding running the 32 bit version on the 64 bit server?

    Thanks

  • Because it is 32 bit, it can only address the first 4gb of memory. Since the OS uses a portion of this memory, it is further restricted. I also think you take a performance hit because it is running via WOW, but I cannot confirm this.

  • After watching the performance on this is appears that dtexec.exe uses very little memory and cpu.

    I never gave this much thought but DTEXEC is generally issuing commands to SQL so the heavy lifting is happening there. It does not appear that dtexec requires much in the way of resources.

    I am running quite a few stored procedures in the ssis package.

  • You are somewhat wrong.

    SSIS can use a lot of memory. For example, use an OLEDB source for a billion records and then a SORT component. This will cause all of the records to buffer in memory.

    Data in the data flow can use a substantial amount of memory, so how a package is designed will make a huge difference.

  • Ok,

    I should not have assumed by what I saw in perfmon.

    I have always assumed doing something like a merge join would actually issue a command to sql which would do the join and return the results using temp tables in the background especially when dealing with large amounts of data.

  • No.

    Integration Services is it's own application. You don't even need to have a connection to a SQL Server.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply