Hot answers tagged ssis
Alright so I believe you doing and INSERT is increasing the size then after you do your OLEDB command which is sending hundreds of thousands of DELETE commands to SQL Server is what's causing your problem. So here is a short Demo/Tutorial on how to do this DELETE operation more effectively. Even if this doesn't solve your index problem it will make your ...
You've got a couple of questions in here: 1) Any ideas on why the SQL Server process would not be following the limit set on the server? Max server memory refers to the buffer pool, but not everything that the server uses memory for. For example, SSIS isn't part of the SQL Server engine - it's another application that just happens to come free in the box ...
There's nothing I've encountered that provides out of the box capability for this and I'll be delighted if someone proves me wrong. Therefore, what I do is a controlled failure. My lookup against DimEmployee should always yield a match. Data was loaded to that table before this dependent package executed. There's no opportunity for source data to change ...
The maximum server limit is just for the buffer pool! Try (unless you are using numa): dbcc memorystatus If that isn't enough: there are a lot of DMVs like dm_os_performance_counters, dm_os_process_memory, dm_os_memory_clerks, dm_os_memory_cache_counters
Only top voted, non community-wiki answers of a minimum length are eligible