May 13, 2008 at 9:20 am
coastliner (5/13/2008)
I monitored with sysinternal Process Explorer and discovered that , apart the Main SQL Service, the other does not take as much memory, and I think I could disable some of them without problem.For the moment I Want to try with 4 GB RAM.
BTW 4GB is not the maximum adressable memory space for a 32bit system ???????
Without using AWE 32bit windows can only allocate 2gb RAM to any single process. the reason people say use 4gb is so that the OS can have 2 and sql can use 2. you can use the 3gb switch which will allow sql to use 1gb more and take it off the OS.
May 13, 2008 at 9:25 am
I had a SQL Server with my previous employer that had 16GB of RAM installed using AWE. I had SQL Server setup to use a max of 14GB and it used every bit of it. The 2GB limit for SQL Server applies to 2000 and older. 2005 will use the addressable limit on the system.
May 13, 2008 at 9:28 am
jim.powers (5/13/2008)
I had a SQL Server with my previous employer that had 16GB of RAM installed using AWE. I had SQL Server setup to use a max of 14GB and it used every bit of it. The 2GB limit for SQL Server applies to 2000 and older. 2005 will use the addressable limit on the system.
Was that a 64-bit machine?
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
May 13, 2008 at 9:30 am
No, it was a 32-bit machine.
May 13, 2008 at 9:33 am
OK I disabled The SQL analisys service, the full text search, the SQL integration service and the reporting service (I did not install the SQL package and I assume that who did that had left active all the possible options!!).
Memory Occupation is (Task Manager) approximately 1.2 GB ... so I think that with 4GB RAM I should go fine !!
What d'ya think?????
May 13, 2008 at 9:34 am
You will need Integration Services if you create maintenance plans in SSMS since they use SSIS. SSIS is also used to transfering data in and out if you need that functionality.
May 13, 2008 at 9:35 am
jim.powers (5/13/2008)
You will need Integration Services if you create maintenance plans in SSMS since they use SSIS. SSIS is also used to transfering data in and out if you need that functionality.
not since SP2, Maint plans no longer require SSIS
May 13, 2008 at 9:38 am
not since SP2, Maint plans no longer require SSIS
That is certainly good to know! Interesting enough, though, even with SP2, it still stores them in SSIS.
May 13, 2008 at 9:42 am
jim.powers (5/13/2008)
No, it was a 32-bit machine.
Unless you enabled AWE, that's mathematically impossible.
The 32-bit address space simply does not have the capacity to reach that kind of memory...
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
May 13, 2008 at 9:43 am
What I need is to have the possibility to schedule backups...so I left active the SQL server Agent. Stop.
BTW I was always told of a 4GB limit on 32bit machine... so I do not quite understand how 8GB, 12GB or 16GB RAM can be exploited.
I do not know nothing about 3GB switch , AWE and all that stuff
To sum UP ...2GB-> 4GB RAM and left the memory option as they are ( or put the max at 2048 MB). STOP
Anyone in accord with me ????
May 13, 2008 at 9:46 am
Marios Philippopoulos (5/13/2008)
jim.powers (5/13/2008)
No, it was a 32-bit machine.Unless you enabled AWE, that's mathematically impossible.
The 32-bit address space simply does not have the capacity to reach that kind of memory...
I did have AWE enabled. I thought I said that in that original post. Sorry if I missed it.
May 13, 2008 at 9:49 am
If you had AWE enabled, then it's no different than sql 2000.
Thanks for clarifying.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
May 13, 2008 at 9:54 am
I mean ..Anyone agree with me ???
May 13, 2008 at 9:56 am
coastliner (5/13/2008)
What I need is to have the possibility to schedule backups...so I left active the SQL server Agent. Stop.BTW I was always told of a 4GB limit on 32bit machine... so I do not quite understand how 8GB, 12GB or 16GB RAM can be exploited.
I do not know nothing about 3GB switch , AWE and all that stuff
To sum UP ...2GB-> 4GB RAM and left the memory option as they are ( or put the max at 2048 MB). STOP
Anyone in accord with me ????
Sounds fine to me.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
May 13, 2008 at 9:56 am
coastliner (5/13/2008)
What I need is to have the possibility to schedule backups...so I left active the SQL server Agent. Stop.BTW I was always told of a 4GB limit on 32bit machine... so I do not quite understand how 8GB, 12GB or 16GB RAM can be exploited.
I do not know nothing about 3GB switch , AWE and all that stuff
To sum UP ...2GB-> 4GB RAM and left the memory option as they are ( or put the max at 2048 MB). STOP
Anyone in accord with me ????
Yes, this will work.
Viewing 15 posts - 31 through 45 (of 47 total)
You must be logged in to reply to this topic. Login to reply