Timeline for Increasing max server memory to deal with System.OutOfMemoryException on SQL Server
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 8, 2017 at 0:30 | comment | added | ana ng | I marked your answer as correct because I was able to find a way to increase the max server memory. I was also able to import the document in smaller batches. However when I attempted to use a UNION query to combine all the smaller tables (the results of my smaller batches) the error popped up again. So I guess technically the question was resolved as far as how I posed the question is concerned. Its just that the crux of the issue is still there. Sould I remove the checkmark for answer? | |
| Mar 8, 2017 at 0:27 | comment | added | Joe Obbish | @anang, I see that you marked my answer as accepted. Is your problem resolved? If not I think that we have a communication problem here. When I say "BULK INSERT" I mean using this command: msdn.microsoft.com/en-us/library/ms188365.aspx . Can you give us more details on how you are importing the data? Are you using SSMS? Which version? Are you generating scripts to insert the data? | |
| Mar 7, 2017 at 23:03 | vote | accept | ana ng | ||
| Mar 7, 2017 at 22:14 | comment | added | ana ng | I have lessened the amount of rows I import at a time. Unfortunately by the time I import my last series of rows into the table I get the server memory issue all over again. | |
| Mar 7, 2017 at 3:34 | history | answered | Joe Obbish | CC BY-SA 3.0 |