We are upgrading to 2005 and have decided to go to a mirrored 2005
environment. We have picked out the production server (principal) 16
gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
having difficulty finding out how "beefy" a box we need for the Witness
server. Does anyone have any experience with this and can you assist me
in specs. I am working with our Network Administrator.
Thanks for all the help!
KristinaAm 11 Jan 2007 06:32:20 -0800 schrieb KristinaDBA@.gmail.com:
> We are upgrading to 2005 and have decided to go to a mirrored 2005
> environment. We have picked out the production server (principal) 16
> gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
> having difficulty finding out how "beefy" a box we need for the Witness
> server. Does anyone have any experience with this and can you assist me
> in specs. I am working with our Network Administrator.
> Thanks for all the help!
> Kristina
Hi, the whitness Server don't need to be so big ;-)
You should install the right editon of SQL Server to be Witness.
The relevance of your sizing are the other roles/jobs this server will do
beside beeing witness.
thats my opinion. hope I could help a little
greetings
Rouven|||Hi,
Kristina - your witness server can be a single processor box with
1/2 GB memory. You can even use SQL Server express. The resources
needed for the witness server is minimum.
This from our Microsoft pre-sales rep.
hth
KristinaDBA@.gmail.com wrote:
> We are upgrading to 2005 and have decided to go to a mirrored 2005
> environment. We have picked out the production server (principal) 16
> gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
> having difficulty finding out how "beefy" a box we need for the Witness
> server. Does anyone have any experience with this and can you assist me
> in specs. I am working with our Network Administrator.
> Thanks for all the help!
> Kristina|||Hey - thanks everyone for the help! I love this group!
JoeyD wrote:[vbcol=seagreen]
> Hi,
> Kristina - your witness server can be a single processor box with
> 1/2 GB memory. You can even use SQL Server express. The resources
> needed for the witness server is minimum.
> This from our Microsoft pre-sales rep.
> hth
>
> KristinaDBA@.gmail.com wrote:|||While being a witness is not a very hard job, it is important because when
the witness is down, automatic failover won't happen so while you can get by
without a lot of processor or memory resources, you don't want to use your
kid's old game machine for this. Get a good quality machine with a good NIC
card and maybe even a UPS.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
<KristinaDBA@.gmail.com> wrote in message
news:1168528668.044990.221330@.i56g2000hsf.googlegroups.com...
> Hey - thanks everyone for the help! I love this group!
> JoeyD wrote:
>
Showing posts with label memory. Show all posts
Showing posts with label memory. Show all posts
Wednesday, March 28, 2012
Mirrored databases and Witness server
We are upgrading to 2005 and have decided to go to a mirrored 2005
environment. We have picked out the production server (principal) 16
gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
having difficulty finding out how "beefy" a box we need for the Witness
server. Does anyone have any experience with this and can you assist me
in specs. I am working with our Network Administrator.
Thanks for all the help!
Kristina
Hi,
Kristina - your witness server can be a single processor box with
1/2 GB memory. You can even use SQL Server express. The resources
needed for the witness server is minimum.
This from our Microsoft pre-sales rep.
hth
KristinaDBA@.gmail.com wrote:
> We are upgrading to 2005 and have decided to go to a mirrored 2005
> environment. We have picked out the production server (principal) 16
> gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
> having difficulty finding out how "beefy" a box we need for the Witness
> server. Does anyone have any experience with this and can you assist me
> in specs. I am working with our Network Administrator.
> Thanks for all the help!
> Kristina
|||Hey - thanks everyone for the help! I love this group!
JoeyD wrote:[vbcol=seagreen]
> Hi,
> Kristina - your witness server can be a single processor box with
> 1/2 GB memory. You can even use SQL Server express. The resources
> needed for the witness server is minimum.
> This from our Microsoft pre-sales rep.
> hth
>
> KristinaDBA@.gmail.com wrote:
|||While being a witness is not a very hard job, it is important because when
the witness is down, automatic failover won't happen so while you can get by
without a lot of processor or memory resources, you don't want to use your
kid's old game machine for this. Get a good quality machine with a good NIC
card and maybe even a UPS.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
<KristinaDBA@.gmail.com> wrote in message
news:1168528668.044990.221330@.i56g2000hsf.googlegr oups.com...
> Hey - thanks everyone for the help! I love this group!
> JoeyD wrote:
>
environment. We have picked out the production server (principal) 16
gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
having difficulty finding out how "beefy" a box we need for the Witness
server. Does anyone have any experience with this and can you assist me
in specs. I am working with our Network Administrator.
Thanks for all the help!
Kristina
Hi,
Kristina - your witness server can be a single processor box with
1/2 GB memory. You can even use SQL Server express. The resources
needed for the witness server is minimum.
This from our Microsoft pre-sales rep.
hth
KristinaDBA@.gmail.com wrote:
> We are upgrading to 2005 and have decided to go to a mirrored 2005
> environment. We have picked out the production server (principal) 16
> gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
> having difficulty finding out how "beefy" a box we need for the Witness
> server. Does anyone have any experience with this and can you assist me
> in specs. I am working with our Network Administrator.
> Thanks for all the help!
> Kristina
|||Hey - thanks everyone for the help! I love this group!
JoeyD wrote:[vbcol=seagreen]
> Hi,
> Kristina - your witness server can be a single processor box with
> 1/2 GB memory. You can even use SQL Server express. The resources
> needed for the witness server is minimum.
> This from our Microsoft pre-sales rep.
> hth
>
> KristinaDBA@.gmail.com wrote:
|||While being a witness is not a very hard job, it is important because when
the witness is down, automatic failover won't happen so while you can get by
without a lot of processor or memory resources, you don't want to use your
kid's old game machine for this. Get a good quality machine with a good NIC
card and maybe even a UPS.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
<KristinaDBA@.gmail.com> wrote in message
news:1168528668.044990.221330@.i56g2000hsf.googlegr oups.com...
> Hey - thanks everyone for the help! I love this group!
> JoeyD wrote:
>
Mirrored databases and Witness server
We are upgrading to 2005 and have decided to go to a mirrored 2005
environment. We have picked out the production server (principal) 16
gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
having difficulty finding out how "beefy" a box we need for the Witness
server. Does anyone have any experience with this and can you assist me
in specs. I am working with our Network Administrator.
Thanks for all the help!
KristinaAm 11 Jan 2007 06:32:20 -0800 schrieb KristinaDBA@.gmail.com:
> We are upgrading to 2005 and have decided to go to a mirrored 2005
> environment. We have picked out the production server (principal) 16
> gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
> having difficulty finding out how "beefy" a box we need for the Witness
> server. Does anyone have any experience with this and can you assist me
> in specs. I am working with our Network Administrator.
> Thanks for all the help!
> Kristina
Hi, the whitness Server don't need to be so big ;-)
You should install the right editon of SQL Server to be Witness.
The relevance of your sizing are the other roles/jobs this server will do
beside beeing witness.
thats my opinion. hope I could help a little
greetings
Rouven|||Hi,
Kristina - your witness server can be a single processor box with
1/2 GB memory. You can even use SQL Server express. The resources
needed for the witness server is minimum.
This from our Microsoft pre-sales rep.
hth
KristinaDBA@.gmail.com wrote:
> We are upgrading to 2005 and have decided to go to a mirrored 2005
> environment. We have picked out the production server (principal) 16
> gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
> having difficulty finding out how "beefy" a box we need for the Witness
> server. Does anyone have any experience with this and can you assist me
> in specs. I am working with our Network Administrator.
> Thanks for all the help!
> Kristina|||Hey - thanks everyone for the help! I love this group!
JoeyD wrote:
> Hi,
> Kristina - your witness server can be a single processor box with
> 1/2 GB memory. You can even use SQL Server express. The resources
> needed for the witness server is minimum.
> This from our Microsoft pre-sales rep.
> hth
>
> KristinaDBA@.gmail.com wrote:
> > We are upgrading to 2005 and have decided to go to a mirrored 2005
> > environment. We have picked out the production server (principal) 16
> > gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
> > having difficulty finding out how "beefy" a box we need for the Witness
> > server. Does anyone have any experience with this and can you assist me
> > in specs. I am working with our Network Administrator.
> >
> > Thanks for all the help!
> >
> > Kristina|||While being a witness is not a very hard job, it is important because when
the witness is down, automatic failover won't happen so while you can get by
without a lot of processor or memory resources, you don't want to use your
kid's old game machine for this. Get a good quality machine with a good NIC
card and maybe even a UPS.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
<KristinaDBA@.gmail.com> wrote in message
news:1168528668.044990.221330@.i56g2000hsf.googlegroups.com...
> Hey - thanks everyone for the help! I love this group!
> JoeyD wrote:
>> Hi,
>> Kristina - your witness server can be a single processor box with
>> 1/2 GB memory. You can even use SQL Server express. The resources
>> needed for the witness server is minimum.
>> This from our Microsoft pre-sales rep.
>> hth
>>
>> KristinaDBA@.gmail.com wrote:
>> > We are upgrading to 2005 and have decided to go to a mirrored 2005
>> > environment. We have picked out the production server (principal) 16
>> > gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
>> > having difficulty finding out how "beefy" a box we need for the Witness
>> > server. Does anyone have any experience with this and can you assist me
>> > in specs. I am working with our Network Administrator.
>> >
>> > Thanks for all the help!
>> >
>> > Kristina
>
environment. We have picked out the production server (principal) 16
gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
having difficulty finding out how "beefy" a box we need for the Witness
server. Does anyone have any experience with this and can you assist me
in specs. I am working with our Network Administrator.
Thanks for all the help!
KristinaAm 11 Jan 2007 06:32:20 -0800 schrieb KristinaDBA@.gmail.com:
> We are upgrading to 2005 and have decided to go to a mirrored 2005
> environment. We have picked out the production server (principal) 16
> gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
> having difficulty finding out how "beefy" a box we need for the Witness
> server. Does anyone have any experience with this and can you assist me
> in specs. I am working with our Network Administrator.
> Thanks for all the help!
> Kristina
Hi, the whitness Server don't need to be so big ;-)
You should install the right editon of SQL Server to be Witness.
The relevance of your sizing are the other roles/jobs this server will do
beside beeing witness.
thats my opinion. hope I could help a little
greetings
Rouven|||Hi,
Kristina - your witness server can be a single processor box with
1/2 GB memory. You can even use SQL Server express. The resources
needed for the witness server is minimum.
This from our Microsoft pre-sales rep.
hth
KristinaDBA@.gmail.com wrote:
> We are upgrading to 2005 and have decided to go to a mirrored 2005
> environment. We have picked out the production server (principal) 16
> gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
> having difficulty finding out how "beefy" a box we need for the Witness
> server. Does anyone have any experience with this and can you assist me
> in specs. I am working with our Network Administrator.
> Thanks for all the help!
> Kristina|||Hey - thanks everyone for the help! I love this group!
JoeyD wrote:
> Hi,
> Kristina - your witness server can be a single processor box with
> 1/2 GB memory. You can even use SQL Server express. The resources
> needed for the witness server is minimum.
> This from our Microsoft pre-sales rep.
> hth
>
> KristinaDBA@.gmail.com wrote:
> > We are upgrading to 2005 and have decided to go to a mirrored 2005
> > environment. We have picked out the production server (principal) 16
> > gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
> > having difficulty finding out how "beefy" a box we need for the Witness
> > server. Does anyone have any experience with this and can you assist me
> > in specs. I am working with our Network Administrator.
> >
> > Thanks for all the help!
> >
> > Kristina|||While being a witness is not a very hard job, it is important because when
the witness is down, automatic failover won't happen so while you can get by
without a lot of processor or memory resources, you don't want to use your
kid's old game machine for this. Get a good quality machine with a good NIC
card and maybe even a UPS.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
<KristinaDBA@.gmail.com> wrote in message
news:1168528668.044990.221330@.i56g2000hsf.googlegroups.com...
> Hey - thanks everyone for the help! I love this group!
> JoeyD wrote:
>> Hi,
>> Kristina - your witness server can be a single processor box with
>> 1/2 GB memory. You can even use SQL Server express. The resources
>> needed for the witness server is minimum.
>> This from our Microsoft pre-sales rep.
>> hth
>>
>> KristinaDBA@.gmail.com wrote:
>> > We are upgrading to 2005 and have decided to go to a mirrored 2005
>> > environment. We have picked out the production server (principal) 16
>> > gigs memory, dual proc quad core, Server 2003 Enterprise Edition. I am
>> > having difficulty finding out how "beefy" a box we need for the Witness
>> > server. Does anyone have any experience with this and can you assist me
>> > in specs. I am working with our Network Administrator.
>> >
>> > Thanks for all the help!
>> >
>> > Kristina
>
Wednesday, March 21, 2012
minimum memory per query: how does it work?
Hi,
How does this "minimum memory per query" option work in SQL Server 2005?
Does it have any influence on performance? When it is put higher than the
standard value, does this mean that more memory will be reserved for each
query, and he will have a hard time to run multiple queries at the same
time?
thanks a lot and kind regards,
PieterYou can use sp_configure to set this a desired value. Check SQL Server Books
Online for the exact syntax.
For light weight databases, it may be a good option to try. However, if you
have a large database with long running transactions on massive datasets or
large number of concurrent connections, using min memory settings is not
recommended. In most cases, it is better to leave it to default since the
query processor usually can figure out the optimal memory allocation for
simple queries.
--
Anith
How does this "minimum memory per query" option work in SQL Server 2005?
Does it have any influence on performance? When it is put higher than the
standard value, does this mean that more memory will be reserved for each
query, and he will have a hard time to run multiple queries at the same
time?
thanks a lot and kind regards,
PieterYou can use sp_configure to set this a desired value. Check SQL Server Books
Online for the exact syntax.
For light weight databases, it may be a good option to try. However, if you
have a large database with long running transactions on massive datasets or
large number of concurrent connections, using min memory settings is not
recommended. In most cases, it is better to leave it to default since the
query processor usually can figure out the optimal memory allocation for
simple queries.
--
Anith
Monday, March 19, 2012
min server memory option and memory paging
I have problem with sql memery usage.
In same case sql paging the data to virtual memory on disk and relese physical memory. And if SQL relese physsical memory, he dont consider min server memory (MB) option(4012MB), after relesingsqlserv physical memory usage is only 500MB. And after sqlserv restart his memory usage is only about 500MB.
Perfmon counters:
Pages/sec1450
%Commited Byte in Use 43%
%UsageTotalPage File87%
Available MBytesMemory6480 MB
My server is:9.00.2153.00SP1Standard Edition (64-bit)
Server memory 8GB
sp_configure:
awe enabled0100
min server memory (MB)0214748364740124012
max server memory (MB)16214748364745004500
I have Enabled the Lock Pages in Memory Option( http://msdn2.microsoft.com/en-us/library/ms190730.aspx )
Can you please provide:
1.The output of "dbcc memorystatus" when the server reaches the described state
2. The 1st 100 lines of the errorlog
Thanks, Ron D.
|||Hello
1. My results of dbcc memorystatus:
https://www.just.ee/fail/dl/26%2E01%2E2007%5F16%5F37%5F57%5F19017%5Flogi%2Etxt
2. And sql server log:
01/26/2007 15:28:15,spid1s,Unknown,AppDomain 2 (kraamat.dbo[runtime].1) unloaded.
01/26/2007 15:28:14,spid1s,Unknown,AppDomain 2 (kraamat.dbo[runtime].1) is marked for unload due to memory pressure.
01/26/2007 15:17:58,spid6s,Unknown,SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf] in database [msdb] (4). The OS file handle is 0x0000000000000870. The offset of the latest long I/O is: 0x00000002961000
01/26/2007 15:17:58,spid6s,Unknown,SQL Server has encountered 49 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\sqldata\kraamat1901_data.mdf] in database [kraamat] (5). The OS file handle is 0x000000000000081C. The offset of the latest long I/O is: 0x00001219ee8000
01/26/2007 14:46:23,spid6s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mssqlsystemresource.mdf] in database [mssqlsystemresource] (32767). The OS file handle is 0x0000000000000684. The offset of the latest long I/O is: 0x00000001242000
01/26/2007 14:45:12,spid6s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf] in database [msdb] (4). The OS file handle is 0x0000000000000870. The offset of the latest long I/O is: 0x00000002162000
01/26/2007 14:45:12,spid6s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\tempdb.mdf] in database [tempdb] (2). The OS file handle is 0x000000000000086C. The offset of the latest long I/O is: 0x00000000482000
01/26/2007 14:45:12,spid6s,Unknown,SQL Server has encountered 3 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\sqldata\kraamat1901_data.mdf] in database [kraamat] (5). The OS file handle is 0x000000000000081C. The offset of the latest long I/O is: 0x00001c7cd7e000
01/26/2007 14:45:12,spid6s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\templog.ldf] in database [tempdb] (2). The OS file handle is 0x0000000000000860. The offset of the latest long I/O is: 0x00000000360000
01/26/2007 14:29:11,spid6s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf] in database [msdb] (4). The OS file handle is 0x0000000000000870. The offset of the latest long I/O is: 0x00000000dc1000
01/26/2007 14:29:01,spid6s,Unknown,SQL Server has encountered 4 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\sqldata\kraamat1901_data.mdf] in database [kraamat] (5). The OS file handle is 0x000000000000081C. The offset of the latest long I/O is: 0x00000acb1ea000
01/26/2007 14:22:45,spid25s,Unknown,Changing the status to FLUSH for full-text catalog "cat_isikud" (7) in database "kraamat" (5). This is an informational message only. No user action is required.
01/26/2007 14:22:43,spid69,Unknown,Replication-Replication Snapshot Subsystem: agent SQL50\KRIS-kraamat-kraamat50-1 scheduled for retry. The replication agent had encountered an exception.<nl/>Source: Replication<nl/>Exception Type: Microsoft.SqlServer.Replication.SqlDeadlockException<nl/>Exception Message: Transaction (Process ID 71) was deadlocked on lock resources with another process and has be
01/26/2007 14:10:47,spid6s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf] in database [msdb] (4). The OS file handle is 0x0000000000000870. The offset of the latest long I/O is: 0x00000000889000
01/26/2007 14:10:37,spid6s,Unknown,SQL Server has encountered 16 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\sqldata\kraamat1901_data.mdf] in database [kraamat] (5). The OS file handle is 0x000000000000081C. The offset of the latest long I/O is: 0x00000c30650000
01/26/2007 14:00:51,spid6s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf] in database [msdb] (4). The OS file handle is 0x0000000000000870. The offset of the latest long I/O is: 0x00000000607000
01/26/2007 14:00:41,spid6s,Unknown,SQL Server has encountered 3 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\sqldata\kraamat1901_data.mdf] in database [kraamat] (5). The OS file handle is 0x000000000000081C. The offset of the latest long I/O is: 0x00000ba0d1c000
01/26/2007 13:54:20,spid72,Unknown,AppDomain 2 (kraamat.dbo[runtime].1) created.
01/26/2007 13:54:18,spid72,Unknown,Common language runtime (CLR) functionality initialized using CLR version v2.0.50727 from C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\.
1. Are you sure these are the 1st 100 lines? The typical errorlog start looks like this:
Jan 20 2007 23:42:11 2005.090.9091.00
Copyright (c) 1988-2006 Microsoft Corporation
Developer Edition on Windows NT 5.2 <X86> (Build 3790: Service Pack 1)
2007-01-23 22:52:23.92 Server (c) 2005 Microsoft Corporation.
2007-01-23 22:52:23.92 Server All rights reserved.
2007-01-23 22:52:23.92 Server Server process ID is 5156.
2007-01-23 22:52:23.92 Server Authentication mode is MIXED.
2007-01-23 22:52:23.92 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-01-23 22:52:23.98 Server This instance of SQL Server last reported using a process ID of 4452 at 1/18/2007 12:29:37 PM (local) 1/18/2007 8:29:37 PM (UTC). This is an informational message only; no user action is required.
2007-01-23 22:52:23.98 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-01-23 22:52:23.98 Server Command Line Startup Parameters:
-c
2007-01-23 22:52:24.13 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2. From the dbcc output, it seems that the server is not using locked pages. (AWE allocated is 0). In that case, the server will be subject to paging, and the OS does not respect the min server memory settings, because it doesn't know about them.
Is this a 32-bit or 64-bit server?
Thanks, Ron D.
|||
It is 64bit OS and SQL. According to http://blogs.msdn.com/slavao/archive/2005/11/15/493019.aspx i dont need switch AWE on to use locked pages.
Here is log again:
01/30/2007 03:02:10,spid68,Unknown,AppDomain 4 (kraamat.dbo[runtime].3) created.
01/30/2007 02:46:00,spid1s,Unknown,AppDomain 3 (kraamat.dbo[runtime].2) unloaded.
01/30/2007 02:46:00,spid1s,Unknown,AppDomain 3 (kraamat.dbo[runtime].2) is marked for unload due to memory pressure.
01/30/2007 00:00:49,spid18s,Unknown,This instance of SQL Server has been using a process ID of 5044 since 29.01.2007 12:38:41 (local) 29.01.2007 10:38:41 (UTC). This is an informational message only; no user action is required.
01/29/2007 18:40:10,spid68,Unknown,AppDomain 3 (kraamat.dbo[runtime].2) created.
01/29/2007 18:31:53,spid1s,Unknown,AppDomain 2 (kraamat.dbo[runtime].1) unloaded.
01/29/2007 18:31:53,spid1s,Unknown,AppDomain 2 (kraamat.dbo[runtime].1) is marked for unload due to memory pressure.
01/29/2007 17:10:47,spid5s,Unknown,SQL Server has encountered 4 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf] in database [msdb] (4). The OS file handle is 0x0000000000000904. The offset of the latest long I/O is: 0x00000001222000
01/29/2007 17:10:37,spid5s,Unknown,SQL Server has encountered 72 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\sqldata\kraamat1901_data.mdf] in database [kraamat] (5). The OS file handle is 0x00000000000008D8. The offset of the latest long I/O is: 0x00001e9a434000
01/29/2007 12:48:40,spid5s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mssqlsystemresource.mdf] in database [mssqlsystemresource] (32767). The OS file handle is 0x0000000000000684. The offset of the latest long I/O is: 0x000000013c8000
01/29/2007 12:45:28,spid5s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\Data\distribution153152.MDF] in database [distribution153152] (10). The OS file handle is 0x00000000000008E8. The offset of the latest long I/O is: 0x0000000281c000
01/29/2007 12:44:26,spid5s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf] in database [msdb] (4). The OS file handle is 0x00000000000008D4. The offset of the latest long I/O is: 0x000000001c0000
01/29/2007 12:44:06,spid5s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf] in database [msdb] (4). The OS file handle is 0x0000000000000904. The offset of the latest long I/O is: 0x00000002245000
01/29/2007 12:44:06,spid5s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\sqldata\kraamat1901_data.mdf] in database [kraamat] (5). The OS file handle is 0x00000000000008D8. The offset of the latest long I/O is: 0x000011affe0000
01/29/2007 12:43:12,spid80,Unknown,AppDomain 2 (kraamat.dbo[runtime].1) created.
01/29/2007 12:43:11,spid80,Unknown,Common language runtime (CLR) functionality initialized using CLR version v2.0.50727 from C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\.
01/29/2007 12:39:59,spid66,Unknown,Configuration option 'min server memory (MB)' changed from 2012 to 4012. Run the RECONFIGURE statement to install.
01/29/2007 12:38:59,spid53,Unknown,Using 'xplog70.dll' version '2005.90.2047' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
01/29/2007 12:38:59,spid53,Unknown,Using 'xpsqlbot.dll' version '2005.90.2047' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
01/29/2007 12:38:59,spid53,Unknown,Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
01/29/2007 12:38:41,spid23s,Unknown,Changing the status to FLUSH for full-text catalog "cat_isikud" (7) in database "kraamat" (5). This is an informational message only. No user action is required.
01/29/2007 12:38:41,spid7s,Unknown,Launched startup procedure 'sp_MSrepl_startup'.
01/29/2007 12:38:41,spid7s,Unknown,Recovery is complete. This is an informational message only. No user action is required.
01/29/2007 12:38:41,spid7s,Unknown,Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
01/29/2007 12:38:38,spid21s,Unknown,Recovery is writing a checkpoint in database 'kraamat' (5). This is an informational message only. No user action is required.
01/29/2007 12:38:38,spid21s,Unknown,Analysis of database 'kraamat' (5) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
01/29/2007 12:38:34,spid26s,Unknown,Starting up database 'distribution153152'.
01/29/2007 12:38:34,spid24s,Unknown,Starting up database 'white'.
01/29/2007 12:38:34,spid20s,Unknown,Starting up database 'msdb'.
01/29/2007 12:38:34,spid21s,Unknown,Starting up database 'kraamat'.
01/29/2007 12:38:34,spid25s,Unknown,Starting up database 'distribution'.
01/29/2007 12:38:34,spid23s,Unknown,Starting up database 'pink'.
01/29/2007 12:38:34,spid22s,Unknown,Starting up database 'ASPState'.
01/29/2007 12:38:34,spid52,Unknown,Using 'xpstar90.dll' version '2005.90.2047' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
01/29/2007 12:38:33,Server,Unknown,SQL Server is now ready for client connections. This is an informational message; no user action is required.
01/29/2007 12:38:33,Server,Unknown,The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
01/29/2007 12:38:33,spid14s,Unknown,Service Broker manager has started.
01/29/2007 12:38:33,spid14s,Unknown,The Database Mirroring protocol transport is disabled or not configured.
01/29/2007 12:38:33,spid14s,Unknown,The Service Broker protocol transport is disabled or not configured.
01/29/2007 12:38:33,Server,Unknown,Server named pipe provider is ready to accept connection on [ \\.\pipe\$$\SQL50\MSSQL$kris\sql\query ].
01/29/2007 12:38:33,Server,Unknown,Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\KRIS ].
01/29/2007 12:38:33,Server,Unknown,Server is listening on [ 10.1.6.185 <ipv4> 2188].
01/29/2007 12:38:33,Server,Unknown,A self-generated certificate was successfully loaded for encryption.
01/29/2007 12:38:33,spid11s,Unknown,Starting up database 'tempdb'.
01/29/2007 12:38:33,spid11s,Unknown,Clearing tempdb database.
01/29/2007 12:38:33,spid11s,Unknown,Starting up database 'model'.
01/29/2007 12:38:33,spid7s,Unknown,The NETBIOS name of the local node that is running the server is 'SQLNODE7'. This is an informational message only. No user action is required.
01/29/2007 12:38:33,spid7s,Unknown,Server name is 'SQL50\KRIS'. This is an informational message only. No user action is required.
01/29/2007 12:38:32,spid7s,Unknown,The resource database build version is 9.00.2153. This is an informational message only. No user action is required.
01/29/2007 12:38:32,spid7s,Unknown,Starting up database 'mssqlsystemresource'.
01/29/2007 12:38:32,spid7s,Unknown,SQL Trace ID 1 was started by login "sa".
01/29/2007 12:38:32,spid7s,Unknown,Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
01/29/2007 12:38:31,spid7s,Unknown,Starting up database 'master'.
01/29/2007 12:38:31,Server,Unknown,Database mirroring has been enabled on this instance of SQL Server.
01/29/2007 12:38:31,Server,Unknown,Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
01/29/2007 12:38:28,Server,Unknown,Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
01/29/2007 12:38:28,Server,Unknown,Multinode configuration: node 1: CPU mask: 0x0000000000000003 Active CPU mask: 0x0000000000000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
01/29/2007 12:38:28,Server,Unknown,Multinode configuration: node 0: CPU mask: 0x000000000000000c Active CPU mask: 0x000000000000000c. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
01/29/2007 12:38:28,Server,Unknown,Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
01/29/2007 12:38:28,Server,Unknown,Detected 4 CPUs. This is an informational message; no user action is required.
01/29/2007 12:38:28,Server,Unknown,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
01/29/2007 12:38:28,Server,Unknown,-l S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
01/29/2007 12:38:28,Server,Unknown,-e S:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
01/29/2007 12:38:28,Server,Unknown,-d S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
01/29/2007 12:38:28,Server,Unknown,Registry startup parameters:
01/29/2007 12:38:28,Server,Unknown,This instance of SQL Server last reported using a process ID of 3984 at 29.01.2007 12:38:20 (local) 29.01.2007 10:38:20 (UTC). This is an informational message only; no user action is required.
01/29/2007 12:38:28,Server,Unknown,Logging SQL Server messages in file 'S:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
01/29/2007 12:38:28,Server,Unknown,Server process ID is 5044.
01/29/2007 12:38:28,Server,Unknown,All rights reserved.
01/29/2007 12:38:28,Server,Unknown,(c) 2005 Microsoft Corporation.
01/29/2007 12:38:28,Server,Unknown,Microsoft SQL Server 2005 - 9.00.2153.00 (X64) <nl/> May 9 2006 13:58:37 <nl/> Copyright (c) 1988-2005 Microsoft Corporation<nl/> Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)
Tiitl
|||Here are memory monitoring pictures: https://www.just.ee/fail/dl/30%2E01%2E2007%5F13%5F02%5F27%5F20736%5Fmemory%2Edoc
Server have enough free memory, but sqlserv paging the data to virtual memory and after relesingsqlserv physical memory usage is only 500MB.
|||You are correct that 64-bit SQL Server ignores the AWE setting. What you need to do (for a start), is give the "Lock Pages in Memory" right to the SQL Server Service account. This will keep the OS from paging and let SQL Server control it.
http://glennberrysqlperformance.spaces.live.com/blog/cns!45041418ECCAA960!115.entry
Then, you should see whether you are having problems with single use, ad-hoc queries bloating your procedure cache, and causing internal memory pressure. See the link below for more detail.
http://glennberrysqlperformance.spaces.live.com/blog/cns!45041418ECCAA960!366.entry
min server memory option and memory paging
I have problem with sql memery usage.
In same case sql paging the data to virtual memory on disk and relese physical memory. And if SQL relese physsical memory, he dont consider min server memory (MB) option(4012MB), after relesingsqlserv physical memory usage is only 500MB. And after sqlserv restart his memory usage is only about 500MB.
Perfmon counters:
Pages/sec1450
%Commited Byte in Use 43%
%UsageTotalPage File87%
Available MBytesMemory6480 MB
My server is:9.00.2153.00SP1Standard Edition (64-bit)
Server memory 8GB
sp_configure:
awe enabled0100
min server memory (MB)0214748364740124012
max server memory (MB)16214748364745004500
I have Enabled the Lock Pages in Memory Option( http://msdn2.microsoft.com/en-us/library/ms190730.aspx )
Can you please provide:
1.The output of "dbcc memorystatus" when the server reaches the described state
2. The 1st 100 lines of the errorlog
Thanks, Ron D.
|||Hello
1. My results of dbcc memorystatus:
https://www.just.ee/fail/dl/26%2E01%2E2007%5F16%5F37%5F57%5F19017%5Flogi%2Etxt
2. And sql server log:
01/26/2007 15:28:15,spid1s,Unknown,AppDomain 2 (kraamat.dbo[runtime].1) unloaded.
01/26/2007 15:28:14,spid1s,Unknown,AppDomain 2 (kraamat.dbo[runtime].1) is marked for unload due to memory pressure.
01/26/2007 15:17:58,spid6s,Unknown,SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf] in database [msdb] (4). The OS file handle is 0x0000000000000870. The offset of the latest long I/O is: 0x00000002961000
01/26/2007 15:17:58,spid6s,Unknown,SQL Server has encountered 49 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\sqldata\kraamat1901_data.mdf] in database [kraamat] (5). The OS file handle is 0x000000000000081C. The offset of the latest long I/O is: 0x00001219ee8000
01/26/2007 14:46:23,spid6s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mssqlsystemresource.mdf] in database [mssqlsystemresource] (32767). The OS file handle is 0x0000000000000684. The offset of the latest long I/O is: 0x00000001242000
01/26/2007 14:45:12,spid6s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf] in database [msdb] (4). The OS file handle is 0x0000000000000870. The offset of the latest long I/O is: 0x00000002162000
01/26/2007 14:45:12,spid6s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\tempdb.mdf] in database [tempdb] (2). The OS file handle is 0x000000000000086C. The offset of the latest long I/O is: 0x00000000482000
01/26/2007 14:45:12,spid6s,Unknown,SQL Server has encountered 3 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\sqldata\kraamat1901_data.mdf] in database [kraamat] (5). The OS file handle is 0x000000000000081C. The offset of the latest long I/O is: 0x00001c7cd7e000
01/26/2007 14:45:12,spid6s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\templog.ldf] in database [tempdb] (2). The OS file handle is 0x0000000000000860. The offset of the latest long I/O is: 0x00000000360000
01/26/2007 14:29:11,spid6s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf] in database [msdb] (4). The OS file handle is 0x0000000000000870. The offset of the latest long I/O is: 0x00000000dc1000
01/26/2007 14:29:01,spid6s,Unknown,SQL Server has encountered 4 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\sqldata\kraamat1901_data.mdf] in database [kraamat] (5). The OS file handle is 0x000000000000081C. The offset of the latest long I/O is: 0x00000acb1ea000
01/26/2007 14:22:45,spid25s,Unknown,Changing the status to FLUSH for full-text catalog "cat_isikud" (7) in database "kraamat" (5). This is an informational message only. No user action is required.
01/26/2007 14:22:43,spid69,Unknown,Replication-Replication Snapshot Subsystem: agent SQL50\KRIS-kraamat-kraamat50-1 scheduled for retry. The replication agent had encountered an exception.<nl/>Source: Replication<nl/>Exception Type: Microsoft.SqlServer.Replication.SqlDeadlockException<nl/>Exception Message: Transaction (Process ID 71) was deadlocked on lock resources with another process and has be
01/26/2007 14:10:47,spid6s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf] in database [msdb] (4). The OS file handle is 0x0000000000000870. The offset of the latest long I/O is: 0x00000000889000
01/26/2007 14:10:37,spid6s,Unknown,SQL Server has encountered 16 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\sqldata\kraamat1901_data.mdf] in database [kraamat] (5). The OS file handle is 0x000000000000081C. The offset of the latest long I/O is: 0x00000c30650000
01/26/2007 14:00:51,spid6s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf] in database [msdb] (4). The OS file handle is 0x0000000000000870. The offset of the latest long I/O is: 0x00000000607000
01/26/2007 14:00:41,spid6s,Unknown,SQL Server has encountered 3 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\sqldata\kraamat1901_data.mdf] in database [kraamat] (5). The OS file handle is 0x000000000000081C. The offset of the latest long I/O is: 0x00000ba0d1c000
01/26/2007 13:54:20,spid72,Unknown,AppDomain 2 (kraamat.dbo[runtime].1) created.
01/26/2007 13:54:18,spid72,Unknown,Common language runtime (CLR) functionality initialized using CLR version v2.0.50727 from C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\.
1. Are you sure these are the 1st 100 lines? The typical errorlog start looks like this:
Jan 20 2007 23:42:11 2005.090.9091.00
Copyright (c) 1988-2006 Microsoft Corporation
Developer Edition on Windows NT 5.2 <X86> (Build 3790: Service Pack 1)
2007-01-23 22:52:23.92 Server (c) 2005 Microsoft Corporation.
2007-01-23 22:52:23.92 Server All rights reserved.
2007-01-23 22:52:23.92 Server Server process ID is 5156.
2007-01-23 22:52:23.92 Server Authentication mode is MIXED.
2007-01-23 22:52:23.92 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-01-23 22:52:23.98 Server This instance of SQL Server last reported using a process ID of 4452 at 1/18/2007 12:29:37 PM (local) 1/18/2007 8:29:37 PM (UTC). This is an informational message only; no user action is required.
2007-01-23 22:52:23.98 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-01-23 22:52:23.98 Server Command Line Startup Parameters:
-c
2007-01-23 22:52:24.13 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2. From the dbcc output, it seems that the server is not using locked pages. (AWE allocated is 0). In that case, the server will be subject to paging, and the OS does not respect the min server memory settings, because it doesn't know about them.
Is this a 32-bit or 64-bit server?
Thanks, Ron D.
|||
It is 64bit OS and SQL. According to http://blogs.msdn.com/slavao/archive/2005/11/15/493019.aspx i dont need switch AWE on to use locked pages.
Here is log again:
01/30/2007 03:02:10,spid68,Unknown,AppDomain 4 (kraamat.dbo[runtime].3) created.
01/30/2007 02:46:00,spid1s,Unknown,AppDomain 3 (kraamat.dbo[runtime].2) unloaded.
01/30/2007 02:46:00,spid1s,Unknown,AppDomain 3 (kraamat.dbo[runtime].2) is marked for unload due to memory pressure.
01/30/2007 00:00:49,spid18s,Unknown,This instance of SQL Server has been using a process ID of 5044 since 29.01.2007 12:38:41 (local) 29.01.2007 10:38:41 (UTC). This is an informational message only; no user action is required.
01/29/2007 18:40:10,spid68,Unknown,AppDomain 3 (kraamat.dbo[runtime].2) created.
01/29/2007 18:31:53,spid1s,Unknown,AppDomain 2 (kraamat.dbo[runtime].1) unloaded.
01/29/2007 18:31:53,spid1s,Unknown,AppDomain 2 (kraamat.dbo[runtime].1) is marked for unload due to memory pressure.
01/29/2007 17:10:47,spid5s,Unknown,SQL Server has encountered 4 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf] in database [msdb] (4). The OS file handle is 0x0000000000000904. The offset of the latest long I/O is: 0x00000001222000
01/29/2007 17:10:37,spid5s,Unknown,SQL Server has encountered 72 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\sqldata\kraamat1901_data.mdf] in database [kraamat] (5). The OS file handle is 0x00000000000008D8. The offset of the latest long I/O is: 0x00001e9a434000
01/29/2007 12:48:40,spid5s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mssqlsystemresource.mdf] in database [mssqlsystemresource] (32767). The OS file handle is 0x0000000000000684. The offset of the latest long I/O is: 0x000000013c8000
01/29/2007 12:45:28,spid5s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\Data\distribution153152.MDF] in database [distribution153152] (10). The OS file handle is 0x00000000000008E8. The offset of the latest long I/O is: 0x0000000281c000
01/29/2007 12:44:26,spid5s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf] in database [msdb] (4). The OS file handle is 0x00000000000008D4. The offset of the latest long I/O is: 0x000000001c0000
01/29/2007 12:44:06,spid5s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf] in database [msdb] (4). The OS file handle is 0x0000000000000904. The offset of the latest long I/O is: 0x00000002245000
01/29/2007 12:44:06,spid5s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [S:\sqldata\kraamat1901_data.mdf] in database [kraamat] (5). The OS file handle is 0x00000000000008D8. The offset of the latest long I/O is: 0x000011affe0000
01/29/2007 12:43:12,spid80,Unknown,AppDomain 2 (kraamat.dbo[runtime].1) created.
01/29/2007 12:43:11,spid80,Unknown,Common language runtime (CLR) functionality initialized using CLR version v2.0.50727 from C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\.
01/29/2007 12:39:59,spid66,Unknown,Configuration option 'min server memory (MB)' changed from 2012 to 4012. Run the RECONFIGURE statement to install.
01/29/2007 12:38:59,spid53,Unknown,Using 'xplog70.dll' version '2005.90.2047' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
01/29/2007 12:38:59,spid53,Unknown,Using 'xpsqlbot.dll' version '2005.90.2047' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
01/29/2007 12:38:59,spid53,Unknown,Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
01/29/2007 12:38:41,spid23s,Unknown,Changing the status to FLUSH for full-text catalog "cat_isikud" (7) in database "kraamat" (5). This is an informational message only. No user action is required.
01/29/2007 12:38:41,spid7s,Unknown,Launched startup procedure 'sp_MSrepl_startup'.
01/29/2007 12:38:41,spid7s,Unknown,Recovery is complete. This is an informational message only. No user action is required.
01/29/2007 12:38:41,spid7s,Unknown,Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
01/29/2007 12:38:38,spid21s,Unknown,Recovery is writing a checkpoint in database 'kraamat' (5). This is an informational message only. No user action is required.
01/29/2007 12:38:38,spid21s,Unknown,Analysis of database 'kraamat' (5) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
01/29/2007 12:38:34,spid26s,Unknown,Starting up database 'distribution153152'.
01/29/2007 12:38:34,spid24s,Unknown,Starting up database 'white'.
01/29/2007 12:38:34,spid20s,Unknown,Starting up database 'msdb'.
01/29/2007 12:38:34,spid21s,Unknown,Starting up database 'kraamat'.
01/29/2007 12:38:34,spid25s,Unknown,Starting up database 'distribution'.
01/29/2007 12:38:34,spid23s,Unknown,Starting up database 'pink'.
01/29/2007 12:38:34,spid22s,Unknown,Starting up database 'ASPState'.
01/29/2007 12:38:34,spid52,Unknown,Using 'xpstar90.dll' version '2005.90.2047' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
01/29/2007 12:38:33,Server,Unknown,SQL Server is now ready for client connections. This is an informational message; no user action is required.
01/29/2007 12:38:33,Server,Unknown,The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
01/29/2007 12:38:33,spid14s,Unknown,Service Broker manager has started.
01/29/2007 12:38:33,spid14s,Unknown,The Database Mirroring protocol transport is disabled or not configured.
01/29/2007 12:38:33,spid14s,Unknown,The Service Broker protocol transport is disabled or not configured.
01/29/2007 12:38:33,Server,Unknown,Server named pipe provider is ready to accept connection on [ \\.\pipe\$$\SQL50\MSSQL$kris\sql\query ].
01/29/2007 12:38:33,Server,Unknown,Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\KRIS ].
01/29/2007 12:38:33,Server,Unknown,Server is listening on [ 10.1.6.185 <ipv4> 2188].
01/29/2007 12:38:33,Server,Unknown,A self-generated certificate was successfully loaded for encryption.
01/29/2007 12:38:33,spid11s,Unknown,Starting up database 'tempdb'.
01/29/2007 12:38:33,spid11s,Unknown,Clearing tempdb database.
01/29/2007 12:38:33,spid11s,Unknown,Starting up database 'model'.
01/29/2007 12:38:33,spid7s,Unknown,The NETBIOS name of the local node that is running the server is 'SQLNODE7'. This is an informational message only. No user action is required.
01/29/2007 12:38:33,spid7s,Unknown,Server name is 'SQL50\KRIS'. This is an informational message only. No user action is required.
01/29/2007 12:38:32,spid7s,Unknown,The resource database build version is 9.00.2153. This is an informational message only. No user action is required.
01/29/2007 12:38:32,spid7s,Unknown,Starting up database 'mssqlsystemresource'.
01/29/2007 12:38:32,spid7s,Unknown,SQL Trace ID 1 was started by login "sa".
01/29/2007 12:38:32,spid7s,Unknown,Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
01/29/2007 12:38:31,spid7s,Unknown,Starting up database 'master'.
01/29/2007 12:38:31,Server,Unknown,Database mirroring has been enabled on this instance of SQL Server.
01/29/2007 12:38:31,Server,Unknown,Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
01/29/2007 12:38:28,Server,Unknown,Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
01/29/2007 12:38:28,Server,Unknown,Multinode configuration: node 1: CPU mask: 0x0000000000000003 Active CPU mask: 0x0000000000000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
01/29/2007 12:38:28,Server,Unknown,Multinode configuration: node 0: CPU mask: 0x000000000000000c Active CPU mask: 0x000000000000000c. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
01/29/2007 12:38:28,Server,Unknown,Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
01/29/2007 12:38:28,Server,Unknown,Detected 4 CPUs. This is an informational message; no user action is required.
01/29/2007 12:38:28,Server,Unknown,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
01/29/2007 12:38:28,Server,Unknown,-l S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
01/29/2007 12:38:28,Server,Unknown,-e S:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
01/29/2007 12:38:28,Server,Unknown,-d S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
01/29/2007 12:38:28,Server,Unknown,Registry startup parameters:
01/29/2007 12:38:28,Server,Unknown,This instance of SQL Server last reported using a process ID of 3984 at 29.01.2007 12:38:20 (local) 29.01.2007 10:38:20 (UTC). This is an informational message only; no user action is required.
01/29/2007 12:38:28,Server,Unknown,Logging SQL Server messages in file 'S:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
01/29/2007 12:38:28,Server,Unknown,Server process ID is 5044.
01/29/2007 12:38:28,Server,Unknown,All rights reserved.
01/29/2007 12:38:28,Server,Unknown,(c) 2005 Microsoft Corporation.
01/29/2007 12:38:28,Server,Unknown,Microsoft SQL Server 2005 - 9.00.2153.00 (X64) <nl/> May 9 2006 13:58:37 <nl/> Copyright (c) 1988-2005 Microsoft Corporation<nl/> Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)
Tiitl
|||Here are memory monitoring pictures: https://www.just.ee/fail/dl/30%2E01%2E2007%5F13%5F02%5F27%5F20736%5Fmemory%2Edoc
Server have enough free memory, but sqlserv paging the data to virtual memory and after relesingsqlserv physical memory usage is only 500MB.
|||You are correct that 64-bit SQL Server ignores the AWE setting. What you need to do (for a start), is give the "Lock Pages in Memory" right to the SQL Server Service account. This will keep the OS from paging and let SQL Server control it.
http://glennberrysqlperformance.spaces.live.com/blog/cns!45041418ECCAA960!115.entry
Then, you should see whether you are having problems with single use, ad-hoc queries bloating your procedure cache, and causing internal memory pressure. See the link below for more detail.
http://glennberrysqlperformance.spaces.live.com/blog/cns!45041418ECCAA960!366.entry
min memory per query
I have a VB.NET application which reads thousands of records from a MSDE
Database, processes them, and writes them against a MYSQL Database. I'm
using the MySQL .NET DataProvider for accessing the MYSQL Database. When I
test the application on my lap top (512MB RAM; MSDE Memory limited to 260MB)
I don't get any errors. When I test the same application on another lap top
(2GB Ram; no limits) I get the error message, that there isn't enough memory
for the querz and I should reduce "min memory per query", which is already
at 512KB. On a desktop computer with 512MB Ram I don't get errors. On a
Server with 2GB Ram the application runs fine, but the MSDE reserves about
1.4GB of Ram. If I limit the Ram of the MSDE on that server to 800MB I get
the error message.
On every computer there is installed: Win XP Pro (or Win XP Server for the
server) SP1, MSDE 2000 (same version on each computer), same MySQL
DataProvider version, and .NET 1.1. On my lap top there is also .NET 1.0
installed. I'm working with VS 2002, which is only installed on my lap top.
I didn't get the errors when writing to the MySQL database with ODBC, but I
can't use ODBC because of the MySQL Database version I have to access.
For processing the first third of the records the memory which is used by
the MSDE is about 250MB on each computer. After that the memory usage on my
lap top and on the desktop pc stays at a low level, but on the other lap top
and on the server the memory usage goes through the roof.
I don't have any glue what the problem can be, it seems that the release of
the memory is handled differently on those machines. Can someone give me a
hint where to look for, what to do, or how to recreate the problem on the
other machines? I can't even look for the problem if I can't recreate the
error on my development machine (my lap top).
Any tipps are welcome!
Thanks
Peter
Hi Peter
I don't think the error is the fact that the min value is too high but the
fact that there is not enough memory to complete the query with what's
there.
See
http://msdn.microsoft.com/library/de...rr_2_65pt.asp.
If you look at the query plan, it could be that your stats are out of date,
or that you are missing indexes or unecessary/excessive hashing/sorting is
occuring
http://msdn.microsoft.com/library/de...onfig_68q6.asp
John
"Peter Zentner" <peter@._REM_zentner-online.de> wrote in message
news:%23DvjjHCxEHA.2632@.TK2MSFTNGP10.phx.gbl...
>I have a VB.NET application which reads thousands of records from a MSDE
> Database, processes them, and writes them against a MYSQL Database. I'm
> using the MySQL .NET DataProvider for accessing the MYSQL Database. When I
> test the application on my lap top (512MB RAM; MSDE Memory limited to
> 260MB)
> I don't get any errors. When I test the same application on another lap
> top
> (2GB Ram; no limits) I get the error message, that there isn't enough
> memory
> for the querz and I should reduce "min memory per query", which is already
> at 512KB. On a desktop computer with 512MB Ram I don't get errors. On a
> Server with 2GB Ram the application runs fine, but the MSDE reserves about
> 1.4GB of Ram. If I limit the Ram of the MSDE on that server to 800MB I get
> the error message.
> On every computer there is installed: Win XP Pro (or Win XP Server for the
> server) SP1, MSDE 2000 (same version on each computer), same MySQL
> DataProvider version, and .NET 1.1. On my lap top there is also .NET 1.0
> installed. I'm working with VS 2002, which is only installed on my lap
> top.
> I didn't get the errors when writing to the MySQL database with ODBC, but
> I
> can't use ODBC because of the MySQL Database version I have to access.
> For processing the first third of the records the memory which is used by
> the MSDE is about 250MB on each computer. After that the memory usage on
> my
> lap top and on the desktop pc stays at a low level, but on the other lap
> top
> and on the server the memory usage goes through the roof.
> I don't have any glue what the problem can be, it seems that the release
> of
> the memory is handled differently on those machines. Can someone give me a
> hint where to look for, what to do, or how to recreate the problem on the
> other machines? I can't even look for the problem if I can't recreate the
> error on my development machine (my lap top).
> Any tipps are welcome!
> Thanks
> Peter
>
Database, processes them, and writes them against a MYSQL Database. I'm
using the MySQL .NET DataProvider for accessing the MYSQL Database. When I
test the application on my lap top (512MB RAM; MSDE Memory limited to 260MB)
I don't get any errors. When I test the same application on another lap top
(2GB Ram; no limits) I get the error message, that there isn't enough memory
for the querz and I should reduce "min memory per query", which is already
at 512KB. On a desktop computer with 512MB Ram I don't get errors. On a
Server with 2GB Ram the application runs fine, but the MSDE reserves about
1.4GB of Ram. If I limit the Ram of the MSDE on that server to 800MB I get
the error message.
On every computer there is installed: Win XP Pro (or Win XP Server for the
server) SP1, MSDE 2000 (same version on each computer), same MySQL
DataProvider version, and .NET 1.1. On my lap top there is also .NET 1.0
installed. I'm working with VS 2002, which is only installed on my lap top.
I didn't get the errors when writing to the MySQL database with ODBC, but I
can't use ODBC because of the MySQL Database version I have to access.
For processing the first third of the records the memory which is used by
the MSDE is about 250MB on each computer. After that the memory usage on my
lap top and on the desktop pc stays at a low level, but on the other lap top
and on the server the memory usage goes through the roof.
I don't have any glue what the problem can be, it seems that the release of
the memory is handled differently on those machines. Can someone give me a
hint where to look for, what to do, or how to recreate the problem on the
other machines? I can't even look for the problem if I can't recreate the
error on my development machine (my lap top).
Any tipps are welcome!
Thanks
Peter
Hi Peter
I don't think the error is the fact that the min value is too high but the
fact that there is not enough memory to complete the query with what's
there.
See
http://msdn.microsoft.com/library/de...rr_2_65pt.asp.
If you look at the query plan, it could be that your stats are out of date,
or that you are missing indexes or unecessary/excessive hashing/sorting is
occuring
http://msdn.microsoft.com/library/de...onfig_68q6.asp
John
"Peter Zentner" <peter@._REM_zentner-online.de> wrote in message
news:%23DvjjHCxEHA.2632@.TK2MSFTNGP10.phx.gbl...
>I have a VB.NET application which reads thousands of records from a MSDE
> Database, processes them, and writes them against a MYSQL Database. I'm
> using the MySQL .NET DataProvider for accessing the MYSQL Database. When I
> test the application on my lap top (512MB RAM; MSDE Memory limited to
> 260MB)
> I don't get any errors. When I test the same application on another lap
> top
> (2GB Ram; no limits) I get the error message, that there isn't enough
> memory
> for the querz and I should reduce "min memory per query", which is already
> at 512KB. On a desktop computer with 512MB Ram I don't get errors. On a
> Server with 2GB Ram the application runs fine, but the MSDE reserves about
> 1.4GB of Ram. If I limit the Ram of the MSDE on that server to 800MB I get
> the error message.
> On every computer there is installed: Win XP Pro (or Win XP Server for the
> server) SP1, MSDE 2000 (same version on each computer), same MySQL
> DataProvider version, and .NET 1.1. On my lap top there is also .NET 1.0
> installed. I'm working with VS 2002, which is only installed on my lap
> top.
> I didn't get the errors when writing to the MySQL database with ODBC, but
> I
> can't use ODBC because of the MySQL Database version I have to access.
> For processing the first third of the records the memory which is used by
> the MSDE is about 250MB on each computer. After that the memory usage on
> my
> lap top and on the desktop pc stays at a low level, but on the other lap
> top
> and on the server the memory usage goes through the roof.
> I don't have any glue what the problem can be, it seems that the release
> of
> the memory is handled differently on those machines. Can someone give me a
> hint where to look for, what to do, or how to recreate the problem on the
> other machines? I can't even look for the problem if I can't recreate the
> error on my development machine (my lap top).
> Any tipps are welcome!
> Thanks
> Peter
>
Min & Max Memory in 2005
Is there a best practice for setting the Minimum and Maximum Memory settings
in SQL Server 2005 on a dedicated SQL Server machine. With SQL Server 2000
we set the minimum and maximum memory to be the same value on our large
clustered SQL Server machines. This seemed to work very well. Is the same
true for 2005?
My experience so far has been you should at least set the max server
memory if you are beyond 2GB range, regardless of x86 or x64.
Note...if you are running x64 and have more than once instance, you
will also should to set it for ALL instances if you have more than one
on the box (or cluster in an active/active situation)...otherwise, the
most greedy instance wins out, creating memory pressure on the OS as
well...or so it goes from my experience. SQL will give up memory when
it recieves the out memory messages from the OS, but in the few times
I tested it during our initial deployment, the memory starvation of
one instance created massive slow downs in performance.
On Jun 15, 9:44 am, "Cgal" <cgalle...@.newsgroups.nospam> wrote:
> Is there a best practice for setting the Minimum and Maximum Memory settings
> in SQL Server 2005 on a dedicated SQL Server machine. With SQL Server 2000
> we set the minimum and maximum memory to be the same value on our large
> clustered SQL Server machines. This seemed to work very well. Is the same
> true for 2005?
|||Setting the min and max to the same basically fixes your memory at that
point and doesn't leave room for the OS to share if needed. In general leave
the min at 0 (default) and set the MAX to a value to always leave some for
the OS. Most systems will work fine with MAX at the default if you are not
using AWE but there may be times when you simply want to leave x amount of
memory for the OS and any other apps running on the server. If you are using
AWE and 32 bit you must set it to some value less than MAX because it is not
dynamic and will starve the OS.How much you leave depends on how much you
have and what you are doing.
Andrew J. Kelly SQL MVP
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:%23AqYlN1rHHA.4768@.TK2MSFTNGP02.phx.gbl...
> Is there a best practice for setting the Minimum and Maximum Memory
> settings in SQL Server 2005 on a dedicated SQL Server machine. With SQL
> Server 2000 we set the minimum and maximum memory to be the same value on
> our large clustered SQL Server machines. This seemed to work very well.
> Is the same true for 2005?
>
in SQL Server 2005 on a dedicated SQL Server machine. With SQL Server 2000
we set the minimum and maximum memory to be the same value on our large
clustered SQL Server machines. This seemed to work very well. Is the same
true for 2005?
My experience so far has been you should at least set the max server
memory if you are beyond 2GB range, regardless of x86 or x64.
Note...if you are running x64 and have more than once instance, you
will also should to set it for ALL instances if you have more than one
on the box (or cluster in an active/active situation)...otherwise, the
most greedy instance wins out, creating memory pressure on the OS as
well...or so it goes from my experience. SQL will give up memory when
it recieves the out memory messages from the OS, but in the few times
I tested it during our initial deployment, the memory starvation of
one instance created massive slow downs in performance.
On Jun 15, 9:44 am, "Cgal" <cgalle...@.newsgroups.nospam> wrote:
> Is there a best practice for setting the Minimum and Maximum Memory settings
> in SQL Server 2005 on a dedicated SQL Server machine. With SQL Server 2000
> we set the minimum and maximum memory to be the same value on our large
> clustered SQL Server machines. This seemed to work very well. Is the same
> true for 2005?
|||Setting the min and max to the same basically fixes your memory at that
point and doesn't leave room for the OS to share if needed. In general leave
the min at 0 (default) and set the MAX to a value to always leave some for
the OS. Most systems will work fine with MAX at the default if you are not
using AWE but there may be times when you simply want to leave x amount of
memory for the OS and any other apps running on the server. If you are using
AWE and 32 bit you must set it to some value less than MAX because it is not
dynamic and will starve the OS.How much you leave depends on how much you
have and what you are doing.
Andrew J. Kelly SQL MVP
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:%23AqYlN1rHHA.4768@.TK2MSFTNGP02.phx.gbl...
> Is there a best practice for setting the Minimum and Maximum Memory
> settings in SQL Server 2005 on a dedicated SQL Server machine. With SQL
> Server 2000 we set the minimum and maximum memory to be the same value on
> our large clustered SQL Server machines. This seemed to work very well.
> Is the same true for 2005?
>
Min & Max Memory in 2005
Is there a best practice for setting the Minimum and Maximum Memory settings
in SQL Server 2005 on a dedicated SQL Server machine. With SQL Server 2000
we set the minimum and maximum memory to be the same value on our large
clustered SQL Server machines. This seemed to work very well. Is the same
true for 2005?My experience so far has been you should at least set the max server
memory if you are beyond 2GB range, regardless of x86 or x64.
Note...if you are running x64 and have more than once instance, you
will also should to set it for ALL instances if you have more than one
on the box (or cluster in an active/active situation)...otherwise, the
most greedy instance wins out, creating memory pressure on the OS as
well...or so it goes from my experience. SQL will give up memory when
it recieves the out memory messages from the OS, but in the few times
I tested it during our initial deployment, the memory starvation of
one instance created massive slow downs in performance.
On Jun 15, 9:44 am, "Cgal" <cgalle...@.newsgroups.nospam> wrote:
> Is there a best practice for setting the Minimum and Maximum Memory settings
> in SQL Server 2005 on a dedicated SQL Server machine. With SQL Server 2000
> we set the minimum and maximum memory to be the same value on our large
> clustered SQL Server machines. This seemed to work very well. Is the same
> true for 2005?|||Setting the min and max to the same basically fixes your memory at that
point and doesn't leave room for the OS to share if needed. In general leave
the min at 0 (default) and set the MAX to a value to always leave some for
the OS. Most systems will work fine with MAX at the default if you are not
using AWE but there may be times when you simply want to leave x amount of
memory for the OS and any other apps running on the server. If you are using
AWE and 32 bit you must set it to some value less than MAX because it is not
dynamic and will starve the OS.How much you leave depends on how much you
have and what you are doing.
--
Andrew J. Kelly SQL MVP
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:%23AqYlN1rHHA.4768@.TK2MSFTNGP02.phx.gbl...
> Is there a best practice for setting the Minimum and Maximum Memory
> settings in SQL Server 2005 on a dedicated SQL Server machine. With SQL
> Server 2000 we set the minimum and maximum memory to be the same value on
> our large clustered SQL Server machines. This seemed to work very well.
> Is the same true for 2005?
>
in SQL Server 2005 on a dedicated SQL Server machine. With SQL Server 2000
we set the minimum and maximum memory to be the same value on our large
clustered SQL Server machines. This seemed to work very well. Is the same
true for 2005?My experience so far has been you should at least set the max server
memory if you are beyond 2GB range, regardless of x86 or x64.
Note...if you are running x64 and have more than once instance, you
will also should to set it for ALL instances if you have more than one
on the box (or cluster in an active/active situation)...otherwise, the
most greedy instance wins out, creating memory pressure on the OS as
well...or so it goes from my experience. SQL will give up memory when
it recieves the out memory messages from the OS, but in the few times
I tested it during our initial deployment, the memory starvation of
one instance created massive slow downs in performance.
On Jun 15, 9:44 am, "Cgal" <cgalle...@.newsgroups.nospam> wrote:
> Is there a best practice for setting the Minimum and Maximum Memory settings
> in SQL Server 2005 on a dedicated SQL Server machine. With SQL Server 2000
> we set the minimum and maximum memory to be the same value on our large
> clustered SQL Server machines. This seemed to work very well. Is the same
> true for 2005?|||Setting the min and max to the same basically fixes your memory at that
point and doesn't leave room for the OS to share if needed. In general leave
the min at 0 (default) and set the MAX to a value to always leave some for
the OS. Most systems will work fine with MAX at the default if you are not
using AWE but there may be times when you simply want to leave x amount of
memory for the OS and any other apps running on the server. If you are using
AWE and 32 bit you must set it to some value less than MAX because it is not
dynamic and will starve the OS.How much you leave depends on how much you
have and what you are doing.
--
Andrew J. Kelly SQL MVP
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:%23AqYlN1rHHA.4768@.TK2MSFTNGP02.phx.gbl...
> Is there a best practice for setting the Minimum and Maximum Memory
> settings in SQL Server 2005 on a dedicated SQL Server machine. With SQL
> Server 2000 we set the minimum and maximum memory to be the same value on
> our large clustered SQL Server machines. This seemed to work very well.
> Is the same true for 2005?
>
Min & Max Memory in 2005
Is there a best practice for setting the Minimum and Maximum Memory settings
in SQL Server 2005 on a dedicated SQL Server machine. With SQL Server 2000
we set the minimum and maximum memory to be the same value on our large
clustered SQL Server machines. This seemed to work very well. Is the same
true for 2005?My experience so far has been you should at least set the max server
memory if you are beyond 2GB range, regardless of x86 or x64.
Note...if you are running x64 and have more than once instance, you
will also should to set it for ALL instances if you have more than one
on the box (or cluster in an active/active situation)...otherwise, the
most greedy instance wins out, creating memory pressure on the OS as
well...or so it goes from my experience. SQL will give up memory when
it recieves the out memory messages from the OS, but in the few times
I tested it during our initial deployment, the memory starvation of
one instance created massive slow downs in performance.
On Jun 15, 9:44 am, "Cgal" <cgalle...@.newsgroups.nospam> wrote:
> Is there a best practice for setting the Minimum and Maximum Memory settin
gs
> in SQL Server 2005 on a dedicated SQL Server machine. With SQL Server 200
0
> we set the minimum and maximum memory to be the same value on our large
> clustered SQL Server machines. This seemed to work very well. Is the sam
e
> true for 2005?|||Setting the min and max to the same basically fixes your memory at that
point and doesn't leave room for the OS to share if needed. In general leave
the min at 0 (default) and set the MAX to a value to always leave some for
the OS. Most systems will work fine with MAX at the default if you are not
using AWE but there may be times when you simply want to leave x amount of
memory for the OS and any other apps running on the server. If you are using
AWE and 32 bit you must set it to some value less than MAX because it is not
dynamic and will starve the OS.How much you leave depends on how much you
have and what you are doing.
Andrew J. Kelly SQL MVP
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:%23AqYlN1rHHA.4768@.TK2MSFTNGP02.phx.gbl...
> Is there a best practice for setting the Minimum and Maximum Memory
> settings in SQL Server 2005 on a dedicated SQL Server machine. With SQL
> Server 2000 we set the minimum and maximum memory to be the same value on
> our large clustered SQL Server machines. This seemed to work very well.
> Is the same true for 2005?
>
in SQL Server 2005 on a dedicated SQL Server machine. With SQL Server 2000
we set the minimum and maximum memory to be the same value on our large
clustered SQL Server machines. This seemed to work very well. Is the same
true for 2005?My experience so far has been you should at least set the max server
memory if you are beyond 2GB range, regardless of x86 or x64.
Note...if you are running x64 and have more than once instance, you
will also should to set it for ALL instances if you have more than one
on the box (or cluster in an active/active situation)...otherwise, the
most greedy instance wins out, creating memory pressure on the OS as
well...or so it goes from my experience. SQL will give up memory when
it recieves the out memory messages from the OS, but in the few times
I tested it during our initial deployment, the memory starvation of
one instance created massive slow downs in performance.
On Jun 15, 9:44 am, "Cgal" <cgalle...@.newsgroups.nospam> wrote:
> Is there a best practice for setting the Minimum and Maximum Memory settin
gs
> in SQL Server 2005 on a dedicated SQL Server machine. With SQL Server 200
0
> we set the minimum and maximum memory to be the same value on our large
> clustered SQL Server machines. This seemed to work very well. Is the sam
e
> true for 2005?|||Setting the min and max to the same basically fixes your memory at that
point and doesn't leave room for the OS to share if needed. In general leave
the min at 0 (default) and set the MAX to a value to always leave some for
the OS. Most systems will work fine with MAX at the default if you are not
using AWE but there may be times when you simply want to leave x amount of
memory for the OS and any other apps running on the server. If you are using
AWE and 32 bit you must set it to some value less than MAX because it is not
dynamic and will starve the OS.How much you leave depends on how much you
have and what you are doing.
Andrew J. Kelly SQL MVP
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:%23AqYlN1rHHA.4768@.TK2MSFTNGP02.phx.gbl...
> Is there a best practice for setting the Minimum and Maximum Memory
> settings in SQL Server 2005 on a dedicated SQL Server machine. With SQL
> Server 2000 we set the minimum and maximum memory to be the same value on
> our large clustered SQL Server machines. This seemed to work very well.
> Is the same true for 2005?
>
Subscribe to:
Posts (Atom)