Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
dr223
Constraint Violating Yak Guru
444 Posts |
Posted - 2014-07-07 : 06:14:28
|
Hi, I have a large database with a table of 200 Million records stored in SQL Server 2008 Standard.The server that holds the SQL Server has the following specs;Windows Server 2008 R2 Standard 64-bit. 16GB RAM 4 CPU'sMemory = 500 GB with 220 GB used by the database. SQL ServerSQL Server 2008 Standard Edition At runtime when I try to open a column from the table; i.e., select ConsultationGuidDigest from dbo.Consultation It failed at record 33,554,432 and throws the error message An error occurred while executing batch. Error message is: Exception of type 'System.OutOfMemoryException' was thrown.I googled and the option of output the results as text - same issueOutput the results to a file - is not an option I want to go ahead with with the tasks I have. If, I need to upgrade the specs for SQL Server or do anything to accomodate this so that the tables could open ok - please advice Thank you in advance |
|
James K
Master Smack Fu Yak Hacker
3873 Posts |
Posted - 2014-07-07 : 11:58:26
|
This is not a limitation of SQL Server; it is a limitation of SQL Server Management Studio which is a 32 bit application. What is the purpose of sending 33 million records to the output window of SQL Server Management Studio? I would venture a guess that Microsoft has not tried to improve or increase the capacity of SSMS to output that much volume of data because they couldn't forsee a reason for someone to scroll through that much data in a SSMS window.If outputting to file is not an option, you can try the other alternative - using SQLCMD. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2014-07-08 : 12:40:36
|
Why are you returning all rows of this table to the client? Use bcp if you need all the data for some other task.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
|
|
rajbtm05
Starting Member
3 Posts |
Posted - 2014-07-09 : 03:40:57
|
It's a limitation on SSMS and not with SQL Server. Try restarting the machine hosting SSMS. |
|
|
|
|
|