Hi all, When I try to run a package with OLEDB source and OLEDB Destination. When I run the package in Debugging mode, At the time of Pre-Execute phase It started filling memory in C Drive nearly about 15GB in 5mins Time. Later I find C drive filled 99% which affects other scheduled job So I stopped the package running. Eventhough the memory not cleared. I am still having 99% full on C Drive. Please let me know, How can i get my memory back

Is that a Lookup component in Full Cache mode there?Arthur My Blog

Its a simple OLEDB source with a SQL Command join clause on 16,000 records and 8,000 records. Not sure why this happend. How to clear the blocked memory. I can see TempDB file size is 15GB. How to clean that.

Restart the machine, this clears the TempDb (if you are using SQL Server). Tip: I guess you are running package this on your old laptop, did I guess rights? If yes, do yourself a favor and set the database into simple recovery mode: ALTER DATABASE Mydb SET RECOVERY SIMPLE; Arthur My Blog

I am actually directly running it in the server where SQL Server also installed. It is an existing environment, I started there recently. When I start running the package it starts using the memory which is common, But when I stopped running that It should release the memory right Basically C drive should show me the full space right? What will be the reason why its not returning the occupied memory TempDB - If I restart the server, It effects the users right, are there any alternate solution for this clearing.

The package may want to swap memory to disk, this typically happens on a resource constrained system. Naturally, running any resource extensive operations on a such machine simply is doomed.Arthur My Blog

The package may want to swap memory to disk, this typically happens on a resource constrained system. Naturally, running any resource extensive operations on a such machine simply is doomed.Arthur My Blog