System.OutOfMemoryException when trying to build sql project.

• 
  This is happening to me too for all of our projects, I updated to the latest on Visual Studio and SQL Change Automation and am suddenly getting this.

  Luke_M September 24, 2019 14:27

  - 0 +
• 
  Same issue here. Using visual studio 2019 16.3 which just shipped yesterday

  Fugazzi8 September 24, 2019 15:49

  - 0 +
• 
  Same issue here.  I receive the error in VS2019 (16.3.0), but everything works as expected in VS2017 (15.9.16).
  
  Both Visual Studio instances show that I am using Redgate SQL Change Automation (4.0.19261.10679).

  shawnpaige September 24, 2019 16:53

  - 0 +
• 
  I have a ticket in and haven't heard back. This needs to be addressed asap!

  Fugazzi8 September 24, 2019 18:49

  - 0 +
• 
  The development team is looking into this with priority. Apologies for the inconvenience

  MayaMalakova September 25, 2019 09:17

  - 0 +
• 
  We are investigating how to fix this. As a workaround, open the sqlproj file in the file editor find the flag <GenerateSqlPackage> and set it to False. This will prevent package scripts being generated but it will fix the out of memory issue, while we continue work on this.
  
  

  LubosM September 25, 2019 10:38

  - 0 +
• 
  That flag did not exist in my sqlproj file, but I added it and it still throws the error.

  Fugazzi8 September 25, 2019 19:13

  - 0 +
• 
  I had the setting, changed it and I'm still receiving the out of memory exception
  
  

  adam_toseland September 26, 2019 03:27

  - 0 +
• 
  This morning I have updated the VisualStudio-Extension to Version 4.0.19270.10947. The build process now completes without the OutOfMemoryException, but the size of the package files are completely unacceptable! What's the reason for this? Building my main sqlproj-Migration outputs now a package file with a size of  ~300MB. Building it before -with the same content(!!!)- generated a package file of 2-3MB. I have to support customers via slow VPN connection. Another problem I experienced after update to 4.0.19270.10947: I cannot open old migration scripts from the Visual Studio Solution explorer or from the VS error list. A double click on the item raises now an error msg dialog from Visual Studio: "Failed to create an editor. Value cannot be null. Parameter name: password".

  WoehrMi September 30, 2019 07:36

  - 0 +
• 

  WoehrMi said:

  Another problem I experienced after update to 4.0.19270.10947: I cannot open old migration scripts from the Visual Studio Solution explorer or from the VS error list. A double click on the item raises now an error msg dialog from Visual Studio: "Failed to create an editor. Value cannot be null. Parameter name: password".

  Please could you try opening the database connection window in Visual Studio and testing the database connection. I hope this will fix this issue.
  
  We will look further into the issue you are facing with very large package files. If you are able to open a support ticket here we can look into your specific case. Thanks.

  Ben_Wood September 30, 2019 11:19

  - 0 +
• 
  Yes, this fixed the issue "Failed to create an editor..". Thank you!

  WoehrMi September 30, 2019 12:09

  - 0 +
• 
  Seem to be fixed in the 4.0.19275.11055 version availlable in the extentions manager this morning

  JeffQc October 02, 2019 14:10

  - 0 +
• 

  WoehrMi said:

  Another problem I experienced after update to 4.0.19270.10947: I cannot open old migration scripts from the Visual Studio Solution explorer or from the VS error list. A double click on the item raises now an error msg dialog from Visual Studio: "Failed to create an editor. Value cannot be null. Parameter name: password".

  Please could you try opening the database connection window in Visual Studio and testing the database connection. I hope this will fix this issue.
  
  We will look further into the issue you are facing with very large package files. If you are able to open a support ticket here we can look into your specific case. Thanks.

  Ben_Wood October 04, 2019 08:35

  - 0 +
• 

  WoehrMi said:

  Another problem I experienced after update to 4.0.19270.10947: I cannot open old migration scripts from the Visual Studio Solution explorer or from the VS error list. A double click on the item raises now an error msg dialog from Visual Studio: "Failed to create an editor. Value cannot be null. Parameter name: password".

  Please could you try opening the database connection window in Visual Studio and testing the database connection. I hope this will fix this issue.
  
  We will look further into the issue you are facing with very large package files. If you are able to open a support ticket here we can look into your specific case. Thanks.

  Ben_Wood October 04, 2019 08:35

  - 0 +
• 
  When I attempt to build my Project I recieve the Error:

  Error An error occurred while attempting to generate a package deployment script: Exception of type 'System.OutOfMemoryException' was thrown.
  
  I have noticed that in my Build it is doing the following:
  

  Using SQL Change Automation toolpath: E:\Development\LeisureHub\Main\LeisureHub\packages\ReadyRoll.MSBuild.3.0.18249.1181\tools\SqlChangeAutomation.Data.Schema.Ssdt.targets

  Using SQL Change Automation version: 3.0.18249.1181
  
  

  I have Upgraded to the latest version of the SQL Change Automation 4.0.19275.11055 and still receive this even after testing the database conneciton..
   
  How can I resolve this?

  CHardy October 04, 2019 16:15

  - 0 +
• 
  Version 4.0.19275.11055 fixed the issue for me. The OutOfMemoryException is gone, the size of the package files went back to normal and the file content is now as expected.

  WoehrMi October 07, 2019 09:00

  - 0 +

Add comment

Please sign in to leave a comment.