Hello,
Are there any extension of max memory support ?
At SQL Server 2005.
Express Edition x86 = 1GB
Workgroup Edition x86 = 3GB
Standard Edition x86 = os limit
Standard Edition x64 = 32TB
Developer Edition x86 = os limit
Developer Edition x64 = 32TB
Enterprise Edition x86, x64 = os limitDatacenter Edition x86, x64 = os limit
ref: Memory Supported by the Editions of SQL Server 2005
http://msdn2.microsoft.com/en-US/library/ms143685.aspx
Especially , My wish is.
Express Edition x64 (native, non wow) , and 2GB support.
Workgroup Edition x64 (native, non wow), and 8GB support.
For SQL Express the memory limits will remain the same. I don't know about the other editions. The jury is still out on x64 native Express, keep your fingers crossed.
Mike
|||What I would really like to see is increased database size limits.
|||(akula@.discussions.microsoft.com) writes: > What I would really like to see is increased database size limits. Isn't the limit 4GB? While this not a very big database, I still think it's a reasonable limit for a free product. Yes, it would be nice if SQL Express could handle TB database, but after all MS needs to make money in some way, so that the SQL Server developers can get bread on the table. :-) -- Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||Well the thing about the size limit is that it is simply annoying but easy to bypass. All you have to do is break your large database into several smaller databases and combine the results. I'm not asking for a TB because it wouldn't work well with the memory limitation. But something in the 8GB-32GB range would be helpful especially if you are in a situation where you have a readonly database that is updated quarterly.|||(akula@.discussions.microsoft.com) writes: > Well the thing about the size limit is that it is simply annoying but > easy to bypass. All you have to do is break your large database into > several smaller databases and combine the results. I'm not asking for a > TB because it wouldn't work well with the memory limitation. But > something in the 8GB-32GB range would be helpful especially if you are > in a situation where you have a readonly database that is updated > quarterly. Each time you get annoyed, think of the license fee you paid! :-) Whatever limit there is, there will always be a point where you need to decide: apply a kludge or cough up money for a paid-for edition? -- Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
No comments:
Post a Comment