Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
can initially set up, but when I go back into and hit OK, I get the following
error:
Error 8114: Error converting data type into to tinyint.
This happens whether I make any changes or not. The job fails with the
basic sqlmaint.exe error:
Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 42000]
(Error 22029). The step failed.
Also, when I try to set the amount of time after which to purge backup
files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
I saw this same issue on some other websites, but no one had an answer. Any
advice? Thanks.
I can't remember what the 8114 error is but the unpopulated
days, weeks, months on the backups was sometimes related to
a missing registry value for the backup directory.
On a default instance, you would add a new string value to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer
The new string value is BackupDirectory
The data value for this is the path to your backup
directory. The default would be
C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP
-Sue
On Mon, 27 Jun 2005 11:50:03 -0700, MEB
<MEB@.discussions.microsoft.com> wrote:
>Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
>can initially set up, but when I go back into and hit OK, I get the following
>error:
>Error 8114: Error converting data type into to tinyint.
>This happens whether I make any changes or not. The job fails with the
>basic sqlmaint.exe error:
>Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 42000]
>(Error 22029). The step failed.
>Also, when I try to set the amount of time after which to purge backup
>files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
>I saw this same issue on some other websites, but no one had an answer. Any
>advice? Thanks.
Showing posts with label sp3. Show all posts
Showing posts with label sp3. Show all posts
Sunday, March 11, 2012
8114 error w/db maintenance plan
Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
can initially set up, but when I go back into and hit OK, I get the following
error:
Error 8114: Error converting data type into to tinyint.
This happens whether I make any changes or not. The job fails with the
basic sqlmaint.exe error:
Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 42000]
(Error 22029). The step failed.
Also, when I try to set the amount of time after which to purge backup
files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
I saw this same issue on some other websites, but no one had an answer. Any
advice? Thanks.I can't remember what the 8114 error is but the unpopulated
days, weeks, months on the backups was sometimes related to
a missing registry value for the backup directory.
On a default instance, you would add a new string value to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer
The new string value is BackupDirectory
The data value for this is the path to your backup
directory. The default would be
C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP
-Sue
On Mon, 27 Jun 2005 11:50:03 -0700, MEB
<MEB@.discussions.microsoft.com> wrote:
>Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
>can initially set up, but when I go back into and hit OK, I get the following
>error:
>Error 8114: Error converting data type into to tinyint.
>This happens whether I make any changes or not. The job fails with the
>basic sqlmaint.exe error:
>Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 42000]
>(Error 22029). The step failed.
>Also, when I try to set the amount of time after which to purge backup
>files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
>I saw this same issue on some other websites, but no one had an answer. Any
>advice? Thanks.
can initially set up, but when I go back into and hit OK, I get the following
error:
Error 8114: Error converting data type into to tinyint.
This happens whether I make any changes or not. The job fails with the
basic sqlmaint.exe error:
Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 42000]
(Error 22029). The step failed.
Also, when I try to set the amount of time after which to purge backup
files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
I saw this same issue on some other websites, but no one had an answer. Any
advice? Thanks.I can't remember what the 8114 error is but the unpopulated
days, weeks, months on the backups was sometimes related to
a missing registry value for the backup directory.
On a default instance, you would add a new string value to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer
The new string value is BackupDirectory
The data value for this is the path to your backup
directory. The default would be
C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP
-Sue
On Mon, 27 Jun 2005 11:50:03 -0700, MEB
<MEB@.discussions.microsoft.com> wrote:
>Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
>can initially set up, but when I go back into and hit OK, I get the following
>error:
>Error 8114: Error converting data type into to tinyint.
>This happens whether I make any changes or not. The job fails with the
>basic sqlmaint.exe error:
>Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 42000]
>(Error 22029). The step failed.
>Also, when I try to set the amount of time after which to purge backup
>files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
>I saw this same issue on some other websites, but no one had an answer. Any
>advice? Thanks.
8114 error w/db maintenance plan
Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
can initially set up, but when I go back into and hit OK, I get the followin
g
error:
Error 8114: Error converting data type into to tinyint.
This happens whether I make any changes or not. The job fails with the
basic sqlmaint.exe error:
Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 420
00]
(Error 22029). The step failed.
Also, when I try to set the amount of time after which to purge backup
files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
I saw this same issue on some other websites, but no one had an answer. Any
advice? Thanks.I can't remember what the 8114 error is but the unpopulated
days, weeks, months on the backups was sometimes related to
a missing registry value for the backup directory.
On a default instance, you would add a new string value to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer
The new string value is BackupDirectory
The data value for this is the path to your backup
directory. The default would be
C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP
-Sue
On Mon, 27 Jun 2005 11:50:03 -0700, MEB
<MEB@.discussions.microsoft.com> wrote:
>Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
>can initially set up, but when I go back into and hit OK, I get the followi
ng
>error:
>Error 8114: Error converting data type into to tinyint.
>This happens whether I make any changes or not. The job fails with the
>basic sqlmaint.exe error:
>Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 42
000]
>(Error 22029). The step failed.
>Also, when I try to set the amount of time after which to purge backup
>files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
>I saw this same issue on some other websites, but no one had an answer. An
y
>advice? Thanks.
can initially set up, but when I go back into and hit OK, I get the followin
g
error:
Error 8114: Error converting data type into to tinyint.
This happens whether I make any changes or not. The job fails with the
basic sqlmaint.exe error:
Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 420
00]
(Error 22029). The step failed.
Also, when I try to set the amount of time after which to purge backup
files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
I saw this same issue on some other websites, but no one had an answer. Any
advice? Thanks.I can't remember what the 8114 error is but the unpopulated
days, weeks, months on the backups was sometimes related to
a missing registry value for the backup directory.
On a default instance, you would add a new string value to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer
The new string value is BackupDirectory
The data value for this is the path to your backup
directory. The default would be
C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP
-Sue
On Mon, 27 Jun 2005 11:50:03 -0700, MEB
<MEB@.discussions.microsoft.com> wrote:
>Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
>can initially set up, but when I go back into and hit OK, I get the followi
ng
>error:
>Error 8114: Error converting data type into to tinyint.
>This happens whether I make any changes or not. The job fails with the
>basic sqlmaint.exe error:
>Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 42
000]
>(Error 22029). The step failed.
>Also, when I try to set the amount of time after which to purge backup
>files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
>I saw this same issue on some other websites, but no one had an answer. An
y
>advice? Thanks.
8007007F error
I have searched this forum about the subject error, but no updated soluation.
The system is windows2000 advanced server SP3 with SQL2000 standard edition SP3. I did a same computer upgrade to windows2003 enterprise edition. After upgrading, the above error appears when I try to view table data from enterprise manager. This problem happens only on the server locally.
I suspect MDAC version is the cause. But MDAC could not be downgraded. Anyone could help?
Thanks in advance, mikeI found the answer by searching the internet forum.
1. here is the link to the detailed steps
http://dbforums.com/t763447.html
2. instead of the dll file in above steps, replacing it with the latest MDAC2.8 version.
That is it!
The problem is that when upgrading from Windows 2000 server to 2003 server the oledb32.dll didnâ't not get updated with the current version from mdac 2.8.
The system is windows2000 advanced server SP3 with SQL2000 standard edition SP3. I did a same computer upgrade to windows2003 enterprise edition. After upgrading, the above error appears when I try to view table data from enterprise manager. This problem happens only on the server locally.
I suspect MDAC version is the cause. But MDAC could not be downgraded. Anyone could help?
Thanks in advance, mikeI found the answer by searching the internet forum.
1. here is the link to the detailed steps
http://dbforums.com/t763447.html
2. instead of the dll file in above steps, replacing it with the latest MDAC2.8 version.
That is it!
The problem is that when upgrading from Windows 2000 server to 2003 server the oledb32.dll didnâ't not get updated with the current version from mdac 2.8.
Sunday, February 19, 2012
6.5 Upgrade
Did as directed in article 818550 and still does not
work. Have two machines, one SS 6.5sp5a on Win 2k other
SS 2000 sp3 on Win 2k.
Now receiving in the application event viewer:
...
Error return from function CreateFile
in file CnvPipe.cpp
Line=143
rc=2
Msg=The system cannot find the file specified.
HELP.There is another article that describes a similar error:
http://support.microsoft.com/?id=246181.
Hope this helps.
--
Michiel Wories, SQL Server PM
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Lana Stokes" <lana.stokes@.aig.com> wrote in message
news:034101c3974c$829ad640$a401280a@.phx.gbl...
> Did as directed in article 818550 and still does not
> work. Have two machines, one SS 6.5sp5a on Win 2k other
> SS 2000 sp3 on Win 2k.
> Now receiving in the application event viewer:
> ...
> Error return from function CreateFile
> in file CnvPipe.cpp
> Line=143
> rc=2
> Msg=The system cannot find the file specified.
> HELP.
>
work. Have two machines, one SS 6.5sp5a on Win 2k other
SS 2000 sp3 on Win 2k.
Now receiving in the application event viewer:
...
Error return from function CreateFile
in file CnvPipe.cpp
Line=143
rc=2
Msg=The system cannot find the file specified.
HELP.There is another article that describes a similar error:
http://support.microsoft.com/?id=246181.
Hope this helps.
--
Michiel Wories, SQL Server PM
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Lana Stokes" <lana.stokes@.aig.com> wrote in message
news:034101c3974c$829ad640$a401280a@.phx.gbl...
> Did as directed in article 818550 and still does not
> work. Have two machines, one SS 6.5sp5a on Win 2k other
> SS 2000 sp3 on Win 2k.
> Now receiving in the application event viewer:
> ...
> Error return from function CreateFile
> in file CnvPipe.cpp
> Line=143
> rc=2
> Msg=The system cannot find the file specified.
> HELP.
>
5GB memory for SQL server
We are having 6GB of memory on SQL server. How do we ensure that SQL server
uses at least 5 GB of memory?
S/w detail
SQL 2000 with sp3
Windows 2003 (32 bit) no spThis is a multi-part message in MIME format.
--060402090907040201010607
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
boot.ini needs the /pae switch to access memory over 4GB (and /3gb
wouldn't hurt either in this case). You need to reboot for that switch
to take affect.
Also, you need to enable AWE memory for your SQL instance with
sp_configure. That is:
exec sp_configure 'awe enabled', 1
reconfigure
go
Then restart the SQL instance (with the Services Control Manager or NET
STOP/NET START). When you use AWE memory SQL Server won't swap out
pages to disk if you're running low on memory (like it does with dynamic
memory management when the memory is less than 4GB). So Microsoft
recommends to set an upper limit on SQL memory usage with the "max
server memory" sp_configure option. For example, to set a max limit of
5GB for the SQL instance (so you don't kill the O/S and other apps on
the box) you would execute this SQL statement:
exec sp_configure "max server memory" 5120
reconfigure
go
You may as well do the 2 sp_configure statements in the same batch and
then restart the SQL instance to save you restarting SQL twice (minimise
downtime). SQL Books Online has a fair bit of stuff on using AWE memory:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
It's a bit unusual to request that SQL uses "at least" 5GB. SQL will
consume the memory as it needs it (starting at < 100MB), caching data
that's accessed and query plans that get compiled. Why not just let it
do it's thing?
This is a very common question on the sqlserver newsgroups. Maybe I
should blog it (like about a hundred other people already have I'm sure).
--
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Amar wrote:
>We are having 6GB of memory on SQL server. How do we ensure that SQL server
>uses at least 5 GB of memory?
>S/w detail
>SQL 2000 with sp3
>Windows 2003 (32 bit) no sp
>
>
>
--060402090907040201010607
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>boot.ini needs the /pae switch to access memory over 4GB (and /3gb
wouldn't hurt either in this case). You need to reboot for that switch
to take affect.<br>
<br>
Also, you need to enable AWE memory for your SQL instance with
sp_configure. That is:<br>
</tt>
<blockquote><tt>exec sp_configure 'awe enabled', 1</tt><br>
<tt>reconfigure</tt><br>
<tt>go</tt><br>
</blockquote>
<tt>Then restart the SQL instance (with the Services Control Manager or
NET STOP/NET START). When you use AWE memory SQL Server won't swap out
pages to disk if you're running low on memory (like it does with
dynamic memory management when the memory is less than 4GB). So
Microsoft recommends to set an upper limit on SQL memory usage with the
"max server memory" sp_configure option. For example, to set a max
limit of 5GB for the SQL instance (so you don't kill the O/S and other
apps on the box) you would execute this SQL statement:<br>
</tt>
<blockquote><tt>exec sp_configure "max server memory" 5120</tt><br>
<tt>reconfigure</tt><br>
<tt>go</tt><br>
</blockquote>
<tt>You may as well do the 2 sp_configure statements in the same batch
and then restart the SQL instance to save you restarting SQL twice
(minimise downtime). SQL Books Online has a fair bit of stuff on using
AWE memory:<br>
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp</a><br>">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp</a><br>
<br>
It's a bit unusual to request that SQL uses "at least" 5GB. SQL will
consume the memory as it needs it (starting at < 100MB), caching
data that's accessed and query plans that get compiled. Why not just
let it do it's thing?<br>
<br>
This is a very common question on the sqlserver newsgroups. Maybe I
should blog it (like about a hundred other people already have I'm
sure).<br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2">blog:</font><font face="Tahoma" size="2"> <a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Amar wrote:
<blockquote cite="mid6D049C2F-5D53-482C-B076-C0BA30770687@.microsoft.com"
type="cite">
<pre wrap="">We are having 6GB of memory on SQL server. How do we ensure that SQL server
uses at least 5 GB of memory?
S/w detail
SQL 2000 with sp3
Windows 2003 (32 bit) no sp
</pre>
</blockquote>
</body>
</html>
--060402090907040201010607--|||Hi
You need Enterprise Edition of SQL Server 2000 and Enterprise Edition of
Windows Server 2003
And read KB 274750
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750 on how to
configure it.
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Amar" wrote:
> We are having 6GB of memory on SQL server. How do we ensure that SQL server
> uses at least 5 GB of memory?
> S/w detail
> SQL 2000 with sp3
> Windows 2003 (32 bit) no sp
>
>|||Thanks Mike for pointing towards right direction
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> You need Enterprise Edition of SQL Server 2000 and Enterprise Edition of
> Windows Server 2003
> And read KB 274750
> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750 on how to
> configure it.
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Amar" wrote:
> > We are having 6GB of memory on SQL server. How do we ensure that SQL server
> > uses at least 5 GB of memory?
> >
> > S/w detail
> > SQL 2000 with sp3
> > Windows 2003 (32 bit) no sp
> >
> >
> >|||Thanks Mike. Great info. Yes a blog would be ver good.
Amar
"Mike Hodgson" wrote:
> boot.ini needs the /pae switch to access memory over 4GB (and /3gb
> wouldn't hurt either in this case). You need to reboot for that switch
> to take affect.
> Also, you need to enable AWE memory for your SQL instance with
> sp_configure. That is:
> exec sp_configure 'awe enabled', 1
> reconfigure
> go
> Then restart the SQL instance (with the Services Control Manager or NET
> STOP/NET START). When you use AWE memory SQL Server won't swap out
> pages to disk if you're running low on memory (like it does with dynamic
> memory management when the memory is less than 4GB). So Microsoft
> recommends to set an upper limit on SQL memory usage with the "max
> server memory" sp_configure option. For example, to set a max limit of
> 5GB for the SQL instance (so you don't kill the O/S and other apps on
> the box) you would execute this SQL statement:
> exec sp_configure "max server memory" 5120
> reconfigure
> go
> You may as well do the 2 sp_configure statements in the same batch and
> then restart the SQL instance to save you restarting SQL twice (minimise
> downtime). SQL Books Online has a fair bit of stuff on using AWE memory:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
> It's a bit unusual to request that SQL uses "at least" 5GB. SQL will
> consume the memory as it needs it (starting at < 100MB), caching data
> that's accessed and query plans that get compiled. Why not just let it
> do it's thing?
> This is a very common question on the sqlserver newsgroups. Maybe I
> should blog it (like about a hundred other people already have I'm sure).
> --
> *mike hodgson*
> blog: http://sqlnerd.blogspot.com
>
> Amar wrote:
> >We are having 6GB of memory on SQL server. How do we ensure that SQL server
> >uses at least 5 GB of memory?
> >
> >S/w detail
> >SQL 2000 with sp3
> >Windows 2003 (32 bit) no sp
> >
> >
> >
> >
> >
>
uses at least 5 GB of memory?
S/w detail
SQL 2000 with sp3
Windows 2003 (32 bit) no spThis is a multi-part message in MIME format.
--060402090907040201010607
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
boot.ini needs the /pae switch to access memory over 4GB (and /3gb
wouldn't hurt either in this case). You need to reboot for that switch
to take affect.
Also, you need to enable AWE memory for your SQL instance with
sp_configure. That is:
exec sp_configure 'awe enabled', 1
reconfigure
go
Then restart the SQL instance (with the Services Control Manager or NET
STOP/NET START). When you use AWE memory SQL Server won't swap out
pages to disk if you're running low on memory (like it does with dynamic
memory management when the memory is less than 4GB). So Microsoft
recommends to set an upper limit on SQL memory usage with the "max
server memory" sp_configure option. For example, to set a max limit of
5GB for the SQL instance (so you don't kill the O/S and other apps on
the box) you would execute this SQL statement:
exec sp_configure "max server memory" 5120
reconfigure
go
You may as well do the 2 sp_configure statements in the same batch and
then restart the SQL instance to save you restarting SQL twice (minimise
downtime). SQL Books Online has a fair bit of stuff on using AWE memory:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
It's a bit unusual to request that SQL uses "at least" 5GB. SQL will
consume the memory as it needs it (starting at < 100MB), caching data
that's accessed and query plans that get compiled. Why not just let it
do it's thing?
This is a very common question on the sqlserver newsgroups. Maybe I
should blog it (like about a hundred other people already have I'm sure).
--
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Amar wrote:
>We are having 6GB of memory on SQL server. How do we ensure that SQL server
>uses at least 5 GB of memory?
>S/w detail
>SQL 2000 with sp3
>Windows 2003 (32 bit) no sp
>
>
>
--060402090907040201010607
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>boot.ini needs the /pae switch to access memory over 4GB (and /3gb
wouldn't hurt either in this case). You need to reboot for that switch
to take affect.<br>
<br>
Also, you need to enable AWE memory for your SQL instance with
sp_configure. That is:<br>
</tt>
<blockquote><tt>exec sp_configure 'awe enabled', 1</tt><br>
<tt>reconfigure</tt><br>
<tt>go</tt><br>
</blockquote>
<tt>Then restart the SQL instance (with the Services Control Manager or
NET STOP/NET START). When you use AWE memory SQL Server won't swap out
pages to disk if you're running low on memory (like it does with
dynamic memory management when the memory is less than 4GB). So
Microsoft recommends to set an upper limit on SQL memory usage with the
"max server memory" sp_configure option. For example, to set a max
limit of 5GB for the SQL instance (so you don't kill the O/S and other
apps on the box) you would execute this SQL statement:<br>
</tt>
<blockquote><tt>exec sp_configure "max server memory" 5120</tt><br>
<tt>reconfigure</tt><br>
<tt>go</tt><br>
</blockquote>
<tt>You may as well do the 2 sp_configure statements in the same batch
and then restart the SQL instance to save you restarting SQL twice
(minimise downtime). SQL Books Online has a fair bit of stuff on using
AWE memory:<br>
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp</a><br>">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp</a><br>
<br>
It's a bit unusual to request that SQL uses "at least" 5GB. SQL will
consume the memory as it needs it (starting at < 100MB), caching
data that's accessed and query plans that get compiled. Why not just
let it do it's thing?<br>
<br>
This is a very common question on the sqlserver newsgroups. Maybe I
should blog it (like about a hundred other people already have I'm
sure).<br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2">blog:</font><font face="Tahoma" size="2"> <a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Amar wrote:
<blockquote cite="mid6D049C2F-5D53-482C-B076-C0BA30770687@.microsoft.com"
type="cite">
<pre wrap="">We are having 6GB of memory on SQL server. How do we ensure that SQL server
uses at least 5 GB of memory?
S/w detail
SQL 2000 with sp3
Windows 2003 (32 bit) no sp
</pre>
</blockquote>
</body>
</html>
--060402090907040201010607--|||Hi
You need Enterprise Edition of SQL Server 2000 and Enterprise Edition of
Windows Server 2003
And read KB 274750
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750 on how to
configure it.
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Amar" wrote:
> We are having 6GB of memory on SQL server. How do we ensure that SQL server
> uses at least 5 GB of memory?
> S/w detail
> SQL 2000 with sp3
> Windows 2003 (32 bit) no sp
>
>|||Thanks Mike for pointing towards right direction
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> You need Enterprise Edition of SQL Server 2000 and Enterprise Edition of
> Windows Server 2003
> And read KB 274750
> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750 on how to
> configure it.
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Amar" wrote:
> > We are having 6GB of memory on SQL server. How do we ensure that SQL server
> > uses at least 5 GB of memory?
> >
> > S/w detail
> > SQL 2000 with sp3
> > Windows 2003 (32 bit) no sp
> >
> >
> >|||Thanks Mike. Great info. Yes a blog would be ver good.
Amar
"Mike Hodgson" wrote:
> boot.ini needs the /pae switch to access memory over 4GB (and /3gb
> wouldn't hurt either in this case). You need to reboot for that switch
> to take affect.
> Also, you need to enable AWE memory for your SQL instance with
> sp_configure. That is:
> exec sp_configure 'awe enabled', 1
> reconfigure
> go
> Then restart the SQL instance (with the Services Control Manager or NET
> STOP/NET START). When you use AWE memory SQL Server won't swap out
> pages to disk if you're running low on memory (like it does with dynamic
> memory management when the memory is less than 4GB). So Microsoft
> recommends to set an upper limit on SQL memory usage with the "max
> server memory" sp_configure option. For example, to set a max limit of
> 5GB for the SQL instance (so you don't kill the O/S and other apps on
> the box) you would execute this SQL statement:
> exec sp_configure "max server memory" 5120
> reconfigure
> go
> You may as well do the 2 sp_configure statements in the same batch and
> then restart the SQL instance to save you restarting SQL twice (minimise
> downtime). SQL Books Online has a fair bit of stuff on using AWE memory:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
> It's a bit unusual to request that SQL uses "at least" 5GB. SQL will
> consume the memory as it needs it (starting at < 100MB), caching data
> that's accessed and query plans that get compiled. Why not just let it
> do it's thing?
> This is a very common question on the sqlserver newsgroups. Maybe I
> should blog it (like about a hundred other people already have I'm sure).
> --
> *mike hodgson*
> blog: http://sqlnerd.blogspot.com
>
> Amar wrote:
> >We are having 6GB of memory on SQL server. How do we ensure that SQL server
> >uses at least 5 GB of memory?
> >
> >S/w detail
> >SQL 2000 with sp3
> >Windows 2003 (32 bit) no sp
> >
> >
> >
> >
> >
>
Thursday, February 9, 2012
3GB Switch question
I am using the following:
Windows 2003 Enterprise
SQL 2000 Std SP3
6GB Ram
4 CPU's with HT turned on (3.2)
I will be running multiple instances of DB.
What should the entry in boot.ini be to best utilise the resources.
Thanks.Leon
http://support.microsoft.com/kb/274750
"Leon" <Lion@.hotmail.com> wrote in message
news:%23$czIrCTHHA.920@.TK2MSFTNGP05.phx.gbl...
>I am using the following:
> Windows 2003 Enterprise
> SQL 2000 Std SP3
> 6GB Ram
> 4 CPU's with HT turned on (3.2)
> I will be running multiple instances of DB.
> What should the entry in boot.ini be to best utilise the resources.
>
> Thanks.
>|||Thanks
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OL1Fg0CTHHA.2212@.TK2MSFTNGP02.phx.gbl...
> Leon
> http://support.microsoft.com/kb/274750
>
> "Leon" <Lion@.hotmail.com> wrote in message
> news:%23$czIrCTHHA.920@.TK2MSFTNGP05.phx.gbl...
>>I am using the following:
>> Windows 2003 Enterprise
>> SQL 2000 Std SP3
>> 6GB Ram
>> 4 CPU's with HT turned on (3.2)
>> I will be running multiple instances of DB.
>> What should the entry in boot.ini be to best utilise the resources.
>>
>> Thanks.
>|||To add on URI; if it is 64 bit system and SQL Server standard edition 64 bit
; then there is no need to change the memory addreesss space. This is
because 64 bit
can address more memory with out changing the BOOT.INI.
Thanks
Hari
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OL1Fg0CTHHA.2212@.TK2MSFTNGP02.phx.gbl...
> Leon
> http://support.microsoft.com/kb/274750
>
> "Leon" <Lion@.hotmail.com> wrote in message
> news:%23$czIrCTHHA.920@.TK2MSFTNGP05.phx.gbl...
>>I am using the following:
>> Windows 2003 Enterprise
>> SQL 2000 Std SP3
>> 6GB Ram
>> 4 CPU's with HT turned on (3.2)
>> I will be running multiple instances of DB.
>> What should the entry in boot.ini be to best utilise the resources.
>>
>> Thanks.
>|||Guys,
Is this the same for SQL 2005 Enterprise on 2003 Standard R2 server? Do I
need to make any changes to boot.ini? The document in KB is for 2000 SQL and
I can not find anything for 2005 SQL. Please help.
"Hari Prasad" wrote:
> To add on URI; if it is 64 bit system and SQL Server standard edition 64 bit
> ; then there is no need to change the memory addreesss space. This is
> because 64 bit
> can address more memory with out changing the BOOT.INI.
> Thanks
> Hari
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OL1Fg0CTHHA.2212@.TK2MSFTNGP02.phx.gbl...
> > Leon
> > http://support.microsoft.com/kb/274750
> >
> >
> >
> > "Leon" <Lion@.hotmail.com> wrote in message
> > news:%23$czIrCTHHA.920@.TK2MSFTNGP05.phx.gbl...
> >>I am using the following:
> >>
> >> Windows 2003 Enterprise
> >> SQL 2000 Std SP3
> >> 6GB Ram
> >> 4 CPU's with HT turned on (3.2)
> >>
> >> I will be running multiple instances of DB.
> >>
> >> What should the entry in boot.ini be to best utilise the resources.
> >>
> >>
> >>
> >> Thanks.
> >>
> >
> >
>
>|||If it is 32 bit and you want the app (in this case SQL Server) to use 3GB
instead of 2GB of directly addressable memory you need to set the /3GB
switch. But I don't believe Windows2003 Std edition uses more than 2 GB to
begin with. I could be wrong on that part though. But the bottom line is the
OS needs to support the memory before SQL Server can. And starting with
SQL2005 Std Edition and up can use all the memory that the OS can access
given the correct configuration.
--
Andrew J. Kelly SQL MVP
"George" <George@.discussions.microsoft.com> wrote in message
news:F8306B35-4D7A-498E-AE05-7C58442A233B@.microsoft.com...
> Guys,
> Is this the same for SQL 2005 Enterprise on 2003 Standard R2 server? Do I
> need to make any changes to boot.ini? The document in KB is for 2000 SQL
> and
> I can not find anything for 2005 SQL. Please help.
> "Hari Prasad" wrote:
>> To add on URI; if it is 64 bit system and SQL Server standard edition 64
>> bit
>> ; then there is no need to change the memory addreesss space. This is
>> because 64 bit
>> can address more memory with out changing the BOOT.INI.
>> Thanks
>> Hari
>>
>> "Uri Dimant" <urid@.iscar.co.il> wrote in message
>> news:OL1Fg0CTHHA.2212@.TK2MSFTNGP02.phx.gbl...
>> > Leon
>> > http://support.microsoft.com/kb/274750
>> >
>> >
>> >
>> > "Leon" <Lion@.hotmail.com> wrote in message
>> > news:%23$czIrCTHHA.920@.TK2MSFTNGP05.phx.gbl...
>> >>I am using the following:
>> >>
>> >> Windows 2003 Enterprise
>> >> SQL 2000 Std SP3
>> >> 6GB Ram
>> >> 4 CPU's with HT turned on (3.2)
>> >>
>> >> I will be running multiple instances of DB.
>> >>
>> >> What should the entry in boot.ini be to best utilise the resources.
>> >>
>> >>
>> >>
>> >> Thanks.
>> >>
>> >
>> >
>>|||Thank you. Anyone knows how to set this correctly on 2003 Standard Server?
"Andrew J. Kelly" wrote:
> If it is 32 bit and you want the app (in this case SQL Server) to use 3GB
> instead of 2GB of directly addressable memory you need to set the /3GB
> switch. But I don't believe Windows2003 Std edition uses more than 2 GB to
> begin with. I could be wrong on that part though. But the bottom line is the
> OS needs to support the memory before SQL Server can. And starting with
> SQL2005 Std Edition and up can use all the memory that the OS can access
> given the correct configuration.
> --
> Andrew J. Kelly SQL MVP
> "George" <George@.discussions.microsoft.com> wrote in message
> news:F8306B35-4D7A-498E-AE05-7C58442A233B@.microsoft.com...
> > Guys,
> >
> > Is this the same for SQL 2005 Enterprise on 2003 Standard R2 server? Do I
> > need to make any changes to boot.ini? The document in KB is for 2000 SQL
> > and
> > I can not find anything for 2005 SQL. Please help.
> >
> > "Hari Prasad" wrote:
> >
> >> To add on URI; if it is 64 bit system and SQL Server standard edition 64
> >> bit
> >> ; then there is no need to change the memory addreesss space. This is
> >> because 64 bit
> >> can address more memory with out changing the BOOT.INI.
> >>
> >> Thanks
> >> Hari
> >>
> >>
> >> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> >> news:OL1Fg0CTHHA.2212@.TK2MSFTNGP02.phx.gbl...
> >> > Leon
> >> > http://support.microsoft.com/kb/274750
> >> >
> >> >
> >> >
> >> > "Leon" <Lion@.hotmail.com> wrote in message
> >> > news:%23$czIrCTHHA.920@.TK2MSFTNGP05.phx.gbl...
> >> >>I am using the following:
> >> >>
> >> >> Windows 2003 Enterprise
> >> >> SQL 2000 Std SP3
> >> >> 6GB Ram
> >> >> 4 CPU's with HT turned on (3.2)
> >> >>
> >> >> I will be running multiple instances of DB.
> >> >>
> >> >> What should the entry in boot.ini be to best utilise the resources.
> >> >>
> >> >>
> >> >>
> >> >> Thanks.
> >> >>
> >> >
> >> >
> >>
> >>
> >>
>
>|||You might want to have a look at these. The concepts are the same.
http://sqljunkies.com/Tutorial/0D4FF40A-695C-4327-A41B-F9F2FE2D58F6.scuk
Memory
http://www.sql-server-performance.com/awe_memory.asp Using AWE Memory
http://www.support.microsoft.com/?id=321363 SQL Server 7 & 2000 memory
usage
http://www.support.microsoft.com/?id=274750 Memory config
http://www.support.microsoft.com/?id=283037 Large Memory Support Is
Available in Windows 2000 (AWE)
http://www.support.microsoft.com/?id=811891 Can not use more than 2GB of
memory
--
Andrew J. Kelly SQL MVP
"George" <George@.discussions.microsoft.com> wrote in message
news:602610CF-D97C-4E87-81F0-1B9E6BC615C3@.microsoft.com...
> Thank you. Anyone knows how to set this correctly on 2003 Standard Server?
> "Andrew J. Kelly" wrote:
>> If it is 32 bit and you want the app (in this case SQL Server) to use 3GB
>> instead of 2GB of directly addressable memory you need to set the /3GB
>> switch. But I don't believe Windows2003 Std edition uses more than 2 GB
>> to
>> begin with. I could be wrong on that part though. But the bottom line is
>> the
>> OS needs to support the memory before SQL Server can. And starting with
>> SQL2005 Std Edition and up can use all the memory that the OS can access
>> given the correct configuration.
>> --
>> Andrew J. Kelly SQL MVP
>> "George" <George@.discussions.microsoft.com> wrote in message
>> news:F8306B35-4D7A-498E-AE05-7C58442A233B@.microsoft.com...
>> > Guys,
>> >
>> > Is this the same for SQL 2005 Enterprise on 2003 Standard R2 server? Do
>> > I
>> > need to make any changes to boot.ini? The document in KB is for 2000
>> > SQL
>> > and
>> > I can not find anything for 2005 SQL. Please help.
>> >
>> > "Hari Prasad" wrote:
>> >
>> >> To add on URI; if it is 64 bit system and SQL Server standard edition
>> >> 64
>> >> bit
>> >> ; then there is no need to change the memory addreesss space. This is
>> >> because 64 bit
>> >> can address more memory with out changing the BOOT.INI.
>> >>
>> >> Thanks
>> >> Hari
>> >>
>> >>
>> >> "Uri Dimant" <urid@.iscar.co.il> wrote in message
>> >> news:OL1Fg0CTHHA.2212@.TK2MSFTNGP02.phx.gbl...
>> >> > Leon
>> >> > http://support.microsoft.com/kb/274750
>> >> >
>> >> >
>> >> >
>> >> > "Leon" <Lion@.hotmail.com> wrote in message
>> >> > news:%23$czIrCTHHA.920@.TK2MSFTNGP05.phx.gbl...
>> >> >>I am using the following:
>> >> >>
>> >> >> Windows 2003 Enterprise
>> >> >> SQL 2000 Std SP3
>> >> >> 6GB Ram
>> >> >> 4 CPU's with HT turned on (3.2)
>> >> >>
>> >> >> I will be running multiple instances of DB.
>> >> >>
>> >> >> What should the entry in boot.ini be to best utilise the resources.
>> >> >>
>> >> >>
>> >> >>
>> >> >> Thanks.
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >>
>>
Windows 2003 Enterprise
SQL 2000 Std SP3
6GB Ram
4 CPU's with HT turned on (3.2)
I will be running multiple instances of DB.
What should the entry in boot.ini be to best utilise the resources.
Thanks.Leon
http://support.microsoft.com/kb/274750
"Leon" <Lion@.hotmail.com> wrote in message
news:%23$czIrCTHHA.920@.TK2MSFTNGP05.phx.gbl...
>I am using the following:
> Windows 2003 Enterprise
> SQL 2000 Std SP3
> 6GB Ram
> 4 CPU's with HT turned on (3.2)
> I will be running multiple instances of DB.
> What should the entry in boot.ini be to best utilise the resources.
>
> Thanks.
>|||Thanks
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OL1Fg0CTHHA.2212@.TK2MSFTNGP02.phx.gbl...
> Leon
> http://support.microsoft.com/kb/274750
>
> "Leon" <Lion@.hotmail.com> wrote in message
> news:%23$czIrCTHHA.920@.TK2MSFTNGP05.phx.gbl...
>>I am using the following:
>> Windows 2003 Enterprise
>> SQL 2000 Std SP3
>> 6GB Ram
>> 4 CPU's with HT turned on (3.2)
>> I will be running multiple instances of DB.
>> What should the entry in boot.ini be to best utilise the resources.
>>
>> Thanks.
>|||To add on URI; if it is 64 bit system and SQL Server standard edition 64 bit
; then there is no need to change the memory addreesss space. This is
because 64 bit
can address more memory with out changing the BOOT.INI.
Thanks
Hari
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OL1Fg0CTHHA.2212@.TK2MSFTNGP02.phx.gbl...
> Leon
> http://support.microsoft.com/kb/274750
>
> "Leon" <Lion@.hotmail.com> wrote in message
> news:%23$czIrCTHHA.920@.TK2MSFTNGP05.phx.gbl...
>>I am using the following:
>> Windows 2003 Enterprise
>> SQL 2000 Std SP3
>> 6GB Ram
>> 4 CPU's with HT turned on (3.2)
>> I will be running multiple instances of DB.
>> What should the entry in boot.ini be to best utilise the resources.
>>
>> Thanks.
>|||Guys,
Is this the same for SQL 2005 Enterprise on 2003 Standard R2 server? Do I
need to make any changes to boot.ini? The document in KB is for 2000 SQL and
I can not find anything for 2005 SQL. Please help.
"Hari Prasad" wrote:
> To add on URI; if it is 64 bit system and SQL Server standard edition 64 bit
> ; then there is no need to change the memory addreesss space. This is
> because 64 bit
> can address more memory with out changing the BOOT.INI.
> Thanks
> Hari
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OL1Fg0CTHHA.2212@.TK2MSFTNGP02.phx.gbl...
> > Leon
> > http://support.microsoft.com/kb/274750
> >
> >
> >
> > "Leon" <Lion@.hotmail.com> wrote in message
> > news:%23$czIrCTHHA.920@.TK2MSFTNGP05.phx.gbl...
> >>I am using the following:
> >>
> >> Windows 2003 Enterprise
> >> SQL 2000 Std SP3
> >> 6GB Ram
> >> 4 CPU's with HT turned on (3.2)
> >>
> >> I will be running multiple instances of DB.
> >>
> >> What should the entry in boot.ini be to best utilise the resources.
> >>
> >>
> >>
> >> Thanks.
> >>
> >
> >
>
>|||If it is 32 bit and you want the app (in this case SQL Server) to use 3GB
instead of 2GB of directly addressable memory you need to set the /3GB
switch. But I don't believe Windows2003 Std edition uses more than 2 GB to
begin with. I could be wrong on that part though. But the bottom line is the
OS needs to support the memory before SQL Server can. And starting with
SQL2005 Std Edition and up can use all the memory that the OS can access
given the correct configuration.
--
Andrew J. Kelly SQL MVP
"George" <George@.discussions.microsoft.com> wrote in message
news:F8306B35-4D7A-498E-AE05-7C58442A233B@.microsoft.com...
> Guys,
> Is this the same for SQL 2005 Enterprise on 2003 Standard R2 server? Do I
> need to make any changes to boot.ini? The document in KB is for 2000 SQL
> and
> I can not find anything for 2005 SQL. Please help.
> "Hari Prasad" wrote:
>> To add on URI; if it is 64 bit system and SQL Server standard edition 64
>> bit
>> ; then there is no need to change the memory addreesss space. This is
>> because 64 bit
>> can address more memory with out changing the BOOT.INI.
>> Thanks
>> Hari
>>
>> "Uri Dimant" <urid@.iscar.co.il> wrote in message
>> news:OL1Fg0CTHHA.2212@.TK2MSFTNGP02.phx.gbl...
>> > Leon
>> > http://support.microsoft.com/kb/274750
>> >
>> >
>> >
>> > "Leon" <Lion@.hotmail.com> wrote in message
>> > news:%23$czIrCTHHA.920@.TK2MSFTNGP05.phx.gbl...
>> >>I am using the following:
>> >>
>> >> Windows 2003 Enterprise
>> >> SQL 2000 Std SP3
>> >> 6GB Ram
>> >> 4 CPU's with HT turned on (3.2)
>> >>
>> >> I will be running multiple instances of DB.
>> >>
>> >> What should the entry in boot.ini be to best utilise the resources.
>> >>
>> >>
>> >>
>> >> Thanks.
>> >>
>> >
>> >
>>|||Thank you. Anyone knows how to set this correctly on 2003 Standard Server?
"Andrew J. Kelly" wrote:
> If it is 32 bit and you want the app (in this case SQL Server) to use 3GB
> instead of 2GB of directly addressable memory you need to set the /3GB
> switch. But I don't believe Windows2003 Std edition uses more than 2 GB to
> begin with. I could be wrong on that part though. But the bottom line is the
> OS needs to support the memory before SQL Server can. And starting with
> SQL2005 Std Edition and up can use all the memory that the OS can access
> given the correct configuration.
> --
> Andrew J. Kelly SQL MVP
> "George" <George@.discussions.microsoft.com> wrote in message
> news:F8306B35-4D7A-498E-AE05-7C58442A233B@.microsoft.com...
> > Guys,
> >
> > Is this the same for SQL 2005 Enterprise on 2003 Standard R2 server? Do I
> > need to make any changes to boot.ini? The document in KB is for 2000 SQL
> > and
> > I can not find anything for 2005 SQL. Please help.
> >
> > "Hari Prasad" wrote:
> >
> >> To add on URI; if it is 64 bit system and SQL Server standard edition 64
> >> bit
> >> ; then there is no need to change the memory addreesss space. This is
> >> because 64 bit
> >> can address more memory with out changing the BOOT.INI.
> >>
> >> Thanks
> >> Hari
> >>
> >>
> >> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> >> news:OL1Fg0CTHHA.2212@.TK2MSFTNGP02.phx.gbl...
> >> > Leon
> >> > http://support.microsoft.com/kb/274750
> >> >
> >> >
> >> >
> >> > "Leon" <Lion@.hotmail.com> wrote in message
> >> > news:%23$czIrCTHHA.920@.TK2MSFTNGP05.phx.gbl...
> >> >>I am using the following:
> >> >>
> >> >> Windows 2003 Enterprise
> >> >> SQL 2000 Std SP3
> >> >> 6GB Ram
> >> >> 4 CPU's with HT turned on (3.2)
> >> >>
> >> >> I will be running multiple instances of DB.
> >> >>
> >> >> What should the entry in boot.ini be to best utilise the resources.
> >> >>
> >> >>
> >> >>
> >> >> Thanks.
> >> >>
> >> >
> >> >
> >>
> >>
> >>
>
>|||You might want to have a look at these. The concepts are the same.
http://sqljunkies.com/Tutorial/0D4FF40A-695C-4327-A41B-F9F2FE2D58F6.scuk
Memory
http://www.sql-server-performance.com/awe_memory.asp Using AWE Memory
http://www.support.microsoft.com/?id=321363 SQL Server 7 & 2000 memory
usage
http://www.support.microsoft.com/?id=274750 Memory config
http://www.support.microsoft.com/?id=283037 Large Memory Support Is
Available in Windows 2000 (AWE)
http://www.support.microsoft.com/?id=811891 Can not use more than 2GB of
memory
--
Andrew J. Kelly SQL MVP
"George" <George@.discussions.microsoft.com> wrote in message
news:602610CF-D97C-4E87-81F0-1B9E6BC615C3@.microsoft.com...
> Thank you. Anyone knows how to set this correctly on 2003 Standard Server?
> "Andrew J. Kelly" wrote:
>> If it is 32 bit and you want the app (in this case SQL Server) to use 3GB
>> instead of 2GB of directly addressable memory you need to set the /3GB
>> switch. But I don't believe Windows2003 Std edition uses more than 2 GB
>> to
>> begin with. I could be wrong on that part though. But the bottom line is
>> the
>> OS needs to support the memory before SQL Server can. And starting with
>> SQL2005 Std Edition and up can use all the memory that the OS can access
>> given the correct configuration.
>> --
>> Andrew J. Kelly SQL MVP
>> "George" <George@.discussions.microsoft.com> wrote in message
>> news:F8306B35-4D7A-498E-AE05-7C58442A233B@.microsoft.com...
>> > Guys,
>> >
>> > Is this the same for SQL 2005 Enterprise on 2003 Standard R2 server? Do
>> > I
>> > need to make any changes to boot.ini? The document in KB is for 2000
>> > SQL
>> > and
>> > I can not find anything for 2005 SQL. Please help.
>> >
>> > "Hari Prasad" wrote:
>> >
>> >> To add on URI; if it is 64 bit system and SQL Server standard edition
>> >> 64
>> >> bit
>> >> ; then there is no need to change the memory addreesss space. This is
>> >> because 64 bit
>> >> can address more memory with out changing the BOOT.INI.
>> >>
>> >> Thanks
>> >> Hari
>> >>
>> >>
>> >> "Uri Dimant" <urid@.iscar.co.il> wrote in message
>> >> news:OL1Fg0CTHHA.2212@.TK2MSFTNGP02.phx.gbl...
>> >> > Leon
>> >> > http://support.microsoft.com/kb/274750
>> >> >
>> >> >
>> >> >
>> >> > "Leon" <Lion@.hotmail.com> wrote in message
>> >> > news:%23$czIrCTHHA.920@.TK2MSFTNGP05.phx.gbl...
>> >> >>I am using the following:
>> >> >>
>> >> >> Windows 2003 Enterprise
>> >> >> SQL 2000 Std SP3
>> >> >> 6GB Ram
>> >> >> 4 CPU's with HT turned on (3.2)
>> >> >>
>> >> >> I will be running multiple instances of DB.
>> >> >>
>> >> >> What should the entry in boot.ini be to best utilise the resources.
>> >> >>
>> >> >>
>> >> >>
>> >> >> Thanks.
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >>
>>
Subscribe to:
Posts (Atom)