January 28, 2008 at 2:10 pm
I have a new windows 2003 R2 box with 48 gig of memory. I am running the 32 bit version of sql 2000(I need the dts for now) and Windows 2003. I have my boot.ini set to below
[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003, Enterprise" /fastdetect /pae /NoExecute=OptOut
I have AWE enabled. However when I goto EM and try to change memory it won't let me move the bar. Went to QA and it won't open I get message below
Server: Msg 8651, Level 17, State 1, Procedure sp_configure, Line 42
Could not perform the requested operation because the minimum query memory is not available. Decrease the configured value for the 'min memory per query' server configuration option.
Anyone seen this before?
January 28, 2008 at 3:02 pm
What is your SQL Server service pack version?
January 29, 2008 at 6:44 am
4
January 29, 2008 at 12:47 pm
SQL 2000 SP4 has a bug resticting memory to be used with 4 GB. Did you apply hot fix? You may also need to enable AWE.
January 29, 2008 at 12:53 pm
The issue was too much memory, I removed the memory back to 32 gig and it worked. MS was suprised when this did work after 2 hours on the phone with them
January 30, 2008 at 4:30 pm
So who said you can never have too much memory!
James Horsley
Workflow Consulting Limited
January 31, 2008 at 3:50 am
You do not have to stay on SQL 2000 just because you need DTS.
If you install SQL 2005 and download and install the DTS Designer component you have a fully functioning DTS environment in SQL 2005. DTS Designer is also supported in SQL 2008, so you can upgrade and keep your DTS.
If you install 64-bit SQL 2005, your DTS runs in WoW mode so it could be a bit slower than running natively on a 32-bit OS. On the other hand, 64-bit SQL 2005 on a box your size should significantly out-perform a 32-bit version, more than making up for any performance lag in DTS.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
January 31, 2008 at 8:14 am
Can't upgrade yet, it is a 3rd party app
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply