SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSIS Buffer Error


SSIS Buffer Error

Author
Message
skaggs.andrew
skaggs.andrew
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2270 Visits: 171
Hi,
I am trying to execute a package and I am getting the following error messages:

Error: A buffer failed while allocating 10475488 bytes.
Error: The system reports 95 percent memory load. There are 17179262976 bytes of physical memory with 687333376 bytes free. There are 4294836224 bytes of virtual memory with 420585472 bytes free. The paging file has 21897904128 bytes with 2934136832 bytes free.

I am in the process of testing these packages as part of a migration. In the current existing environment (Server A Visual Studio 2008), I have no issues and everything runs fine.
On the new server (Server B Visual Studio 2017), I am getting this error message.

Any thoughts as to why this is happening?
Phil Parkin
Phil Parkin
SSC Guru
SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)

Group: General Forum Members
Points: 240312 Visits: 25404
skaggs.andrew - Thursday, May 3, 2018 10:54 AM
Hi,
I am trying to execute a package and I am getting the following error messages:

Error: A buffer failed while allocating 10475488 bytes.
Error: The system reports 95 percent memory load. There are 17179262976 bytes of physical memory with 687333376 bytes free. There are 4294836224 bytes of virtual memory with 420585472 bytes free. The paging file has 21897904128 bytes with 2934136832 bytes free.

I am in the process of testing these packages as part of a migration. In the current existing environment (Server A Visual Studio 2008), I have no issues and everything runs fine.
On the new server (Server B Visual Studio 2017), I am getting this error message.

Any thoughts as to why this is happening?

What does the package do?



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.
skaggs.andrew
skaggs.andrew
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2270 Visits: 171
Phil Parkin - Thursday, May 3, 2018 11:08 AM
[quote]
skaggs.andrew - Thursday, May 3, 2018 10:54 AM
Hi,
I am trying to execute a package and I am getting the following error messages:

Error: A buffer failed while allocating 10475488 bytes.
Error: The system reports 95 percent memory load. There are 17179262976 bytes of physical memory with 687333376 bytes free. There are 4294836224 bytes of virtual memory with 420585472 bytes free. The paging file has 21897904128 bytes with 2934136832 bytes free.

I am in the process of testing these packages as part of a migration. In the current existing environment (Server A Visual Studio 2008), I have no issues and everything runs fine.
On the new server (Server B Visual Studio 2017), I am getting this error message.

Any thoughts as to why this is happening?

What does the package do

The package says the execution completed. It acts as though the data flow completed without error. However, when I look at links between the sources and targets within the data flow task, I can see that they have not all completed. It's as if everything stopped and didn't complete the data transfer from source to target

Phil Parkin
Phil Parkin
SSC Guru
SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)

Group: General Forum Members
Points: 240312 Visits: 25404
skaggs.andrew - Thursday, May 3, 2018 11:14 AM

The package says the execution completed. It acts as though the data flow completed without error. However, when I look at links between the sources and targets within the data flow task, I can see that they have not all completed. It's as if everything stopped and didn't complete the data transfer from source to target

Sure, but that's not quite what I meant Smile
Is this just a simple data flow from A to B, or is there more complexity than that (eg, lookups, aggregations, joins)?



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.
skaggs.andrew
skaggs.andrew
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2270 Visits: 171
Phil Parkin - Thursday, May 3, 2018 11:25 AM
skaggs.andrew - Thursday, May 3, 2018 11:14 AM

The package says the execution completed. It acts as though the data flow completed without error. However, when I look at links between the sources and targets within the data flow task, I can see that they have not all completed. It's as if everything stopped and didn't complete the data transfer from source to target

Sure, but that's not quite what I meant Smile
Is this just a simple data flow from A to B, or is there more complexity than that (eg, lookups, aggregations, joins)?

Sorry. This is a very straight forward source to target, no transformations involved. I have a data flow task and inside I have probably 10 source to target paths setup. This has been working for years and now that I have migrated the package, I am getting this error.

sgmunson
sgmunson
SSC Guru
SSC Guru (109K reputation)SSC Guru (109K reputation)SSC Guru (109K reputation)SSC Guru (109K reputation)SSC Guru (109K reputation)SSC Guru (109K reputation)SSC Guru (109K reputation)SSC Guru (109K reputation)

Group: General Forum Members
Points: 109165 Visits: 7531
skaggs.andrew - Thursday, May 3, 2018 11:32 AM
Phil Parkin - Thursday, May 3, 2018 11:25 AM
skaggs.andrew - Thursday, May 3, 2018 11:14 AM

The package says the execution completed. It acts as though the data flow completed without error. However, when I look at links between the sources and targets within the data flow task, I can see that they have not all completed. It's as if everything stopped and didn't complete the data transfer from source to target

Sure, but that's not quite what I meant Smile
Is this just a simple data flow from A to B, or is there more complexity than that (eg, lookups, aggregations, joins)?

Sorry. This is a very straight forward source to target, no transformations involved. I have a data flow task and inside I have probably 10 source to target paths setup. This has been working for years and now that I have migrated the package, I am getting this error.

Do those data flows execute in parallel, or one at a time? Does the physical configuration of the new server (RAM, CPU, DISK SPACE, DRIVE LETTERS) match or exceed the old server's values? Is there a change in the SQL Server version?


Steve
‌(aka sgmunson)
Smile Smile Smile
Health & Nutrition
Phil Parkin
Phil Parkin
SSC Guru
SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)

Group: General Forum Members
Points: 240312 Visits: 25404
skaggs.andrew - Thursday, May 3, 2018 11:32 AM
Phil Parkin - Thursday, May 3, 2018 11:25 AM
skaggs.andrew - Thursday, May 3, 2018 11:14 AM

The package says the execution completed. It acts as though the data flow completed without error. However, when I look at links between the sources and targets within the data flow task, I can see that they have not all completed. It's as if everything stopped and didn't complete the data transfer from source to target

Sure, but that's not quite what I meant Smile
Is this just a simple data flow from A to B, or is there more complexity than that (eg, lookups, aggregations, joins)?

Sorry. This is a very straight forward source to target, no transformations involved. I have a data flow task and inside I have probably 10 source to target paths setup. This has been working for years and now that I have migrated the package, I am getting this error.

No problem.

Was this a straight migration, or were any changes made to the packages? Specifically, values like Rows Per Batch and Maximum Insert Commit Size on the data flow destinations?

Is the RAM on the 2017 machine the same, or larger, than what you have on the 2008 instance?



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.
skaggs.andrew
skaggs.andrew
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2270 Visits: 171
sgmunson - Thursday, May 3, 2018 12:40 PM
skaggs.andrew - Thursday, May 3, 2018 11:32 AM
Phil Parkin - Thursday, May 3, 2018 11:25 AM
skaggs.andrew - Thursday, May 3, 2018 11:14 AM

The package says the execution completed. It acts as though the data flow completed without error. However, when I look at links between the sources and targets within the data flow task, I can see that they have not all completed. It's as if everything stopped and didn't complete the data transfer from source to target

Sure, but that's not quite what I meant Smile
Is this just a simple data flow from A to B, or is there more complexity than that (eg, lookups, aggregations, joins)?

Sorry. This is a very straight forward source to target, no transformations involved. I have a data flow task and inside I have probably 10 source to target paths setup. This has been working for years and now that I have migrated the package, I am getting this error.

Do those data flows execute in parallel, or one at a time? Does the physical configuration of the new server (RAM, CPU, DISK SPACE, DRIVE LETTERS) match or exceed the old server's values? Is there a change in the SQL Server version?

the flows DO execute in parallel. I checked the physical configuration and they appear to be the same. In this process, I have also upgraded to 2017 SQL Server. The previous version is 2008

skaggs.andrew
skaggs.andrew
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2270 Visits: 171
Phil Parkin - Thursday, May 3, 2018 12:45 PM
skaggs.andrew - Thursday, May 3, 2018 11:32 AM
Phil Parkin - Thursday, May 3, 2018 11:25 AM
skaggs.andrew - Thursday, May 3, 2018 11:14 AM

The package says the execution completed. It acts as though the data flow completed without error. However, when I look at links between the sources and targets within the data flow task, I can see that they have not all completed. It's as if everything stopped and didn't complete the data transfer from source to target

Sure, but that's not quite what I meant Smile
Is this just a simple data flow from A to B, or is there more complexity than that (eg, lookups, aggregations, joins)?

Sorry. This is a very straight forward source to target, no transformations involved. I have a data flow task and inside I have probably 10 source to target paths setup. This has been working for years and now that I have migrated the package, I am getting this error.

No problem.

Was this a straight migration, or were any changes made to the packages? Specifically, values like Rows Per Batch and Maximum Insert Commit Size on the data flow destinations?

Is the RAM on the 2017 machine the same, or larger, than what you have on the 2008 instance?

I essentially just copied the packages over from the old environment. Maybe 10 packages in total. I have already tested about 6 of them and no issues until now. I did not make any changes to the package other than configure the connection manager. I have the same amount of RAM on both machines.

Phil Parkin
Phil Parkin
SSC Guru
SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)SSC Guru (240K reputation)

Group: General Forum Members
Points: 240312 Visits: 25404
skaggs.andrew - Thursday, May 3, 2018 12:48 PM
Phil Parkin - Thursday, May 3, 2018 12:45 PM
skaggs.andrew - Thursday, May 3, 2018 11:32 AM
Phil Parkin - Thursday, May 3, 2018 11:25 AM
skaggs.andrew - Thursday, May 3, 2018 11:14 AM

The package says the execution completed. It acts as though the data flow completed without error. However, when I look at links between the sources and targets within the data flow task, I can see that they have not all completed. It's as if everything stopped and didn't complete the data transfer from source to target

Sure, but that's not quite what I meant Smile
Is this just a simple data flow from A to B, or is there more complexity than that (eg, lookups, aggregations, joins)?

Sorry. This is a very straight forward source to target, no transformations involved. I have a data flow task and inside I have probably 10 source to target paths setup. This has been working for years and now that I have migrated the package, I am getting this error.

No problem.

Was this a straight migration, or were any changes made to the packages? Specifically, values like Rows Per Batch and Maximum Insert Commit Size on the data flow destinations?

Is the RAM on the 2017 machine the same, or larger, than what you have on the 2008 instance?

I essentially just copied the packages over from the old environment. Maybe 10 packages in total. I have already tested about 6 of them and no issues until now. I did not make any changes to the package other than configure the connection manager. I have the same amount of RAM on both machines.

OK. What Edition of SQL Server is the 2008 instance (Standard, Enterprise, etc)? Same question for the new server.



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum









































































































































































SQLServerCentral


Search