3G ram for SQL server: memory

Showing posts with label memory. Show all posts

Monday, March 19, 2012

9GB log file generated

Hi
The reporting services is generating large log files of 9GB daily and using
all the virtual memory that all applications on my win2003 server stop
running. Application is running on sql server 2000 and Microsoft Report
Server SP1.
How do I go about trouble-shooting this?
--
Regards PatsyWhich report server log is getting up to 9GB?
Is it the ReportServerTempDB log or ReportServer log? (it better not be the
ReportServer log...)
Or do you mean the actual LOG files in the reportserver directory? (these
are text files)
One thing you can check quickly, make sure the ReportServerTempDB database
is set to simple recovery mode.
=-Chris
"Patsy" <Patsy@.discussions.microsoft.com> wrote in message
news:12B3FCC9-60A3-4F48-B1F0-385B5C2DA7D4@.microsoft.com...
> Hi
> The reporting services is generating large log files of 9GB daily and
> using
> all the virtual memory that all applications on my win2003 server stop
> running. Application is running on sql server 2000 and Microsoft Report
> Server SP1.
> How do I go about trouble-shooting this?
> --
> Regards Patsy|||This is a known issue. You could search this group for -- log hotfix.
One reply from MS said:
Ask product support for the fix associated with KB 885286.
I believe this is fixed in sp2
Patsy wrote:
> Hi
> The reporting services is generating large log files of 9GB daily and using
> all the virtual memory that all applications on my win2003 server stop
> running. Application is running on sql server 2000 and Microsoft Report
> Server SP1.
> How do I go about trouble-shooting this?
> --
> Regards Patsy

8GB memory installation

Situation:
OS: 2000 advanced server
SQL enterprise
We have just added an extra 6GB of memory to our database server which
brings the total to 8. The problem we are having is that the OS is only using
3Gb of memory.
We have run the SP that is recommended for AWE and entered the /3GB /PAE in
the boot.ini file and restarted the machine.
The server still refuses to use more than 3GB. Any ideas?Did you re-configure SQL, the AWE and fixed memory?
e.g.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'min server memory', 6656 (make same as maximum)
RECONFIGURE
go
sp_configure 'max server memory', 6656 (leave at least 512 for the OS)
RECONFIGURE
Regards
Mike
"lramsdale" wrote:
> Situation:
> OS: 2000 advanced server
> SQL enterprise
> We have just added an extra 6GB of memory to our database server which
> brings the total to 8. The problem we are having is that the OS is only using
> 3Gb of memory.
> We have run the SP that is recommended for AWE and entered the /3GB /PAE in
> the boot.ini file and restarted the machine.
> The server still refuses to use more than 3GB. Any ideas?|||This is what we ran:
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
"Mike Epprecht (SQL MVP)" wrote:
> Did you re-configure SQL, the AWE and fixed memory?
> e.g.
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'min server memory', 6656 (make same as maximum)
> RECONFIGURE
> go
> sp_configure 'max server memory', 6656 (leave at least 512 for the OS)
> RECONFIGURE
> Regards
> Mike
> "lramsdale" wrote:
> > Situation:
> >
> > OS: 2000 advanced server
> > SQL enterprise
> >
> > We have just added an extra 6GB of memory to our database server which
> > brings the total to 8. The problem we are having is that the OS is only using
> > 3Gb of memory.
> >
> > We have run the SP that is recommended for AWE and entered the /3GB /PAE in
> > the boot.ini file and restarted the machine.
> >
> > The server still refuses to use more than 3GB. Any ideas?|||Ok we finally got to the bottom of this problem - it seems that we needed to
give the SQL server service account permissions to the lock pages in memory
privelege, even though it was in the domain admin account. This was hard to
find, why is there so much conflicting documentation on this AWE setting?
"lramsdale" wrote:
> This is what we ran:
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> "Mike Epprecht (SQL MVP)" wrote:
> > Did you re-configure SQL, the AWE and fixed memory?
> >
> > e.g.
> >
> > sp_configure 'show advanced options', 1
> > RECONFIGURE
> > GO
> > sp_configure 'awe enabled', 1
> > RECONFIGURE
> > GO
> > sp_configure 'min server memory', 6656 (make same as maximum)
> > RECONFIGURE
> > go
> > sp_configure 'max server memory', 6656 (leave at least 512 for the OS)
> > RECONFIGURE
> >
> > Regards
> > Mike
> >
> > "lramsdale" wrote:
> >
> > > Situation:
> > >
> > > OS: 2000 advanced server
> > > SQL enterprise
> > >
> > > We have just added an extra 6GB of memory to our database server which
> > > brings the total to 8. The problem we are having is that the OS is only using
> > > 3Gb of memory.
> > >
> > > We have run the SP that is recommended for AWE and entered the /3GB /PAE in
> > > the boot.ini file and restarted the machine.
> > >
> > > The server still refuses to use more than 3GB. Any ideas?

Sunday, March 11, 2012

80004005 ODBC SQL Server Driver shared memory or TCP/IP sockets er

Hi all,
I have been getting these errors on simple ASP code on my web site:
|80004005|[Microsoft][ODBC_SQL_Server_Driver][TCP/IP_Sockets]ConnectionWrite_(send()).
|80004005|[Microsoft][ODBC_SQL_Server_Driver]Timeout_expired
|80004005|[Microsoft][ODBC_SQL_Server_Driver][Shared_Memory]SQL_Server_does_not_exist_or_access_denied.
|80004005|[Microsoft][ODBC_SQL_Server_Driver][TCP/IP_Sockets]SQL_Server_does_not_exist_or_access_denied.
|80004005|[Microsoft][ODBC_SQL_Server_Driver]Timeout_expired
The SQL 2000 is Standard Edition, SP3 and OS is Windows 2003 Standard edition.
Previously I never faced this problem before. These errors come
intermittently, at no specific time. It appears randomly at any time.
The only thing I have to do is reboot the server to solve this issue.
please tell me if there's anything to solve this issue.
reboot?
"tapman" wrote:

> Hi all,
> I have been getting these errors on simple ASP code on my web site:
> |80004005|[Microsoft][ODBC_SQL_Server_Driver][TCP/IP_Sockets]ConnectionWrite_(send()).
> |80004005|[Microsoft][ODBC_SQL_Server_Driver]Timeout_expired
> |80004005|[Microsoft][ODBC_SQL_Server_Driver][Shared_Memory]SQL_Server_does_not_exist_or_access_denied.
>
> |80004005|[Microsoft][ODBC_SQL_Server_Driver][TCP/IP_Sockets]SQL_Server_does_not_exist_or_access_denied.
> |80004005|[Microsoft][ODBC_SQL_Server_Driver]Timeout_expired
> The SQL 2000 is Standard Edition, SP3 and OS is Windows 2003 Standard edition.
> Previously I never faced this problem before. These errors come
> intermittently, at no specific time. It appears randomly at any time.
> The only thing I have to do is reboot the server to solve this issue.
> please tell me if there's anything to solve this issue.
>

8 GB of RAM

I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server
Standard.
I have the switches /PAE /3GB in boot.ini
SQL max server memory is = 6656 MB
but with those settings I cannot get SQLServer to get more than 2.7 GB
of RAM
If I use the AWE switch, then SQLServer can only use 128 MB max
What's wrong?
PaulOn Dec 4, 3:42 am, pd...@.clic.net wrote:
> I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server
> Standard.
> I have the switches /PAE /3GB in boot.ini
> SQL max server memory is = 6656 MB
> but with those settings I cannot get SQLServer to get more than 2.7 GB
> of RAM
> If I use the AWE switch, then SQLServer can only use 128 MB max
> What's wrong?
> Paul
Is it SQL Server 2000 or SQL Server 2005?
If its SQL Server 2000, then AWE is not supported
If its SQL Server 2005, then check the AWE 'Run Value' in
sp_configure... if its 0, then you might want to recycle the SQL
Server service to enable the AWE
In any case i dont believe you need to have /3GB switch in boot.ini.|||Hey, of course you can use AWE on SQL Server 2000 (and also on SQL Server
2005).
You will need to run
sp_configure 'awe enabled', 1
and grant the Lock Page in Memory permission to your service account. For
more details see
How to configure SQL Server to use more than 2 GB of physical memory
http://support.microsoft.com/kb/274750
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"dineshbabu.munugala@.gmail.com" wrote:
> On Dec 4, 3:42 am, pd...@.clic.net wrote:
> > I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server
> > Standard.
> > I have the switches /PAE /3GB in boot.ini
> >
> > SQL max server memory is = 6656 MB
> >
> > but with those settings I cannot get SQLServer to get more than 2.7 GB
> > of RAM
> >
> > If I use the AWE switch, then SQLServer can only use 128 MB max
> >
> > What's wrong?
> >
> > Paul
> Is it SQL Server 2000 or SQL Server 2005?
> If its SQL Server 2000, then AWE is not supported
> If its SQL Server 2005, then check the AWE 'Run Value' in
> sp_configure... if its 0, then you might want to recycle the SQL
> Server service to enable the AWE
> In any case i dont believe you need to have /3GB switch in boot.ini.
>|||Ben
If you are on 64-bit , you do not need AWE anymore. If the OP has SQL Server
2000 along with SP4 , make sure that he has a last hotfix especially if he
are going to enable AWE
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:2ADA35D9-C4FA-4852-B20A-3E08F240C626@.microsoft.com...
> Hey, of course you can use AWE on SQL Server 2000 (and also on SQL Server
> 2005).
> You will need to run
> sp_configure 'awe enabled', 1
> and grant the Lock Page in Memory permission to your service account. For
> more details see
> How to configure SQL Server to use more than 2 GB of physical memory
> http://support.microsoft.com/kb/274750
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "dineshbabu.munugala@.gmail.com" wrote:
>> On Dec 4, 3:42 am, pd...@.clic.net wrote:
>> > I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server
>> > Standard.
>> > I have the switches /PAE /3GB in boot.ini
>> >
>> > SQL max server memory is = 6656 MB
>> >
>> > but with those settings I cannot get SQLServer to get more than 2.7 GB
>> > of RAM
>> >
>> > If I use the AWE switch, then SQLServer can only use 128 MB max
>> >
>> > What's wrong?
>> >
>> > Paul
>> Is it SQL Server 2000 or SQL Server 2005?
>> If its SQL Server 2000, then AWE is not supported
>> If its SQL Server 2005, then check the AWE 'Run Value' in
>> sp_configure... if its 0, then you might want to recycle the SQL
>> Server service to enable the AWE
>> In any case i dont believe you need to have /3GB switch in boot.ini.|||On 3 d=E9c, 18:04, dineshbabu.munug...@.gmail.com wrote:
> On Dec 4, 3:42 am, pd...@.clic.net wrote:
> > I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server
> > Standard.
> > I have the switches /PAE /3GB in boot.ini
> > SQL max server memory is =3D 6656 MB
> > but with those settings I cannot get SQLServer to get more than 2.7 GB
> > of RAM
> > If I use the AWE switch, then SQLServer can only use 128 MB max
> > What's wrong?
> > Paul
> Is it SQL Server 2000 or SQL Server 2005?
> If its SQL Server 2000, then AWE is not supported
> If its SQL Server 2005, then check the AWE 'Run Value' in
> sp_configure... if its 0, then you might want to recycle the SQL
> Server service to enable the AWE
> In any case i dont believe you need to have /3GB switch in boot.ini.
SQL2005 Standard.
Running in 32 bits system
As soon as I use AWE, I'm stuck with 128 MB of RAM for SQL server...
(i.e. I run dbcc checkDB so that it starts using rapidly memory and I
see SQLServer.exe using not more than 128 MB of RAM in Task Manager).
Paul|||Hi
Do you have SP4 with hotfix?
Install hotfix from(http://support.microsoft.com/kb/899761)
Do you see in PerfMon that SQL Server allocate 6.6GB RAM?
<pdube@.clic.net> wrote in message
news:e4a9b19a-1b95-4df7-b6d9-e8c374bfb9c0@.a39g2000pre.googlegroups.com...
On 3 déc, 18:04, dineshbabu.munug...@.gmail.com wrote:
> On Dec 4, 3:42 am, pd...@.clic.net wrote:
> > I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server
> > Standard.
> > I have the switches /PAE /3GB in boot.ini
> > SQL max server memory is = 6656 MB
> > but with those settings I cannot get SQLServer to get more than 2.7 GB
> > of RAM
> > If I use the AWE switch, then SQLServer can only use 128 MB max
> > What's wrong?
> > Paul
> Is it SQL Server 2000 or SQL Server 2005?
> If its SQL Server 2000, then AWE is not supported
> If its SQL Server 2005, then check the AWE 'Run Value' in
> sp_configure... if its 0, then you might want to recycle the SQL
> Server service to enable the AWE
> In any case i dont believe you need to have /3GB switch in boot.ini.
SQL2005 Standard.
Running in 32 bits system
As soon as I use AWE, I'm stuck with 128 MB of RAM for SQL server...
(i.e. I run dbcc checkDB so that it starts using rapidly memory and I
see SQLServer.exe using not more than 128 MB of RAM in Task Manager).
Paul|||On 4 d=E9c, 10:45, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Hi
> Do you have SP4 with hotfix?
> Install hotfix from(http://support.microsoft.com/kb/899761)
> Do you see in PerfMon that SQL Server allocate 6.6GB RAM?
> <pd...@.clic.net> wrote in message
> news:e4a9b19a-1b95-4df7-b6d9-e8c374bfb9c0@.a39g2000pre.googlegroups.com...
> On 3 d=E9c, 18:04, dineshbabu.munug...@.gmail.com wrote:
>
>
> > On Dec 4, 3:42 am, pd...@.clic.net wrote:
> > > I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server
> > > Standard.
> > > I have the switches /PAE /3GB in boot.ini
> > > SQL max server memory is =3D 6656 MB
> > > but with those settings I cannot get SQLServer to get more than 2.7 GB=
> > > of RAM
> > > If I use the AWE switch, then SQLServer can only use 128 MB max
> > > What's wrong?
> > > Paul
> > Is it SQL Server 2000 or SQL Server 2005?
> > If its SQL Server 2000, then AWE is not supported
> > If its SQL Server 2005, then check the AWE 'Run Value' in
> > sp_configure... if its 0, then you might want to recycle the SQL
> > Server service to enable the AWE
> > In any case i dont believe you need to have /3GB switch in boot.ini.
> SQL2005 Standard.
> Running in 32 bits system
> As soon as I use AWE, I'm stuck with 128 MB of RAM for SQL server...
> (i.e. I run dbcc checkDB so that it starts using rapidly memory and I
> see SQLServer.exe using not more than 128 MB of RAM in Task Manager).
> Paul- Masquer le texte des messages pr=E9c=E9dents -
> - Afficher le texte des messages pr=E9c=E9dents -
SQL 2005 (9.00.3161.00)
The hotfix is for SQL 2000...
In PerfMon, I see Commited Bytes around 3.2 GB.
In Task Manager I still see SQLServer.exe using 2.7 GB. I guess then
that's just a problem related with Task Manager not showing the
correct amount of RAM used...?
Paul|||On 4 d=E9c, 14:08, pd...@.clic.net wrote:
> On 4 d=E9c, 10:45, "Uri Dimant" <u...@.iscar.co.il> wrote:
>
>
> > Hi
> > Do you have SP4 with hotfix?
> > Install hotfix from(http://support.microsoft.com/kb/899761)
> > Do you see in PerfMon that SQL Server allocate 6.6GB RAM?
> > <pd...@.clic.net> wrote in message
> >news:e4a9b19a-1b95-4df7-b6d9-e8c374bfb9c0@.a39g2000pre.googlegroups.com...=
> > On 3 d=E9c, 18:04, dineshbabu.munug...@.gmail.com wrote:
> > > On Dec 4, 3:42 am, pd...@.clic.net wrote:
> > > > I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server=
> > > > Standard.
> > > > I have the switches /PAE /3GB in boot.ini
> > > > SQL max server memory is =3D 6656 MB
> > > > but with those settings I cannot get SQLServer to get more than 2.7 =GB
> > > > of RAM
> > > > If I use the AWE switch, then SQLServer can only use 128 MB max
> > > > What's wrong?
> > > > Paul
> > > Is it SQL Server 2000 or SQL Server 2005?
> > > If its SQL Server 2000, then AWE is not supported
> > > If its SQL Server 2005, then check the AWE 'Run Value' in
> > > sp_configure... if its 0, then you might want to recycle the SQL
> > > Server service to enable the AWE
> > > In any case i dont believe you need to have /3GB switch in boot.ini.
> > SQL2005 Standard.
> > Running in 32 bits system
> > As soon as I use AWE, I'm stuck with 128 MB of RAM for SQL server...
> > (i.e. I run dbcc checkDB so that it starts using rapidly memory and I
> > see SQLServer.exe using not more than 128 MB of RAM in Task Manager).
> > Paul- Masquer le texte des messages pr=E9c=E9dents -
> > - Afficher le texte des messages pr=E9c=E9dents -
> SQL 2005 (9.00.3161.00)
> The hotfix is for SQL 2000...
> In PerfMon, I see Commited Bytes around 3.2 GB.
> In Task Manager I still see SQLServer.exe using 2.7 GB. I guess then
> that's just a problem related with Task Manager not showing the
> correct amount of RAM used...?
> Paul- Masquer le texte des messages pr=E9c=E9dents -
> - Afficher le texte des messages pr=E9c=E9dents -
When I say that I see 128 MB of RAM in SQLServer.exe when using AWE I
mean that's what I see in Task Manager. Am I correct looking at this
value?
Should I check PerfMon instead? Is the memory shown in TaskManager
only kernel memory and would not show all memory used by SQL?
Paul|||SP4 hotfix is not needed here as this is SQL Server 2005.
Try this to see how much memory SQL Server is using. Performance Monitor,
add SQLServer:Memory Manager - Total Server Memory (KB).
Have you granted the Lock Page in Memory permission to your service account?
See your Error log. Must show 'Address Windowing Extensions enabled' or some
AWE error message.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Uri Dimant" wrote:
> Hi
> Do you have SP4 with hotfix?
> Install hotfix from(http://support.microsoft.com/kb/899761)
> Do you see in PerfMon that SQL Server allocate 6.6GB RAM?
>
>
> <pdube@.clic.net> wrote in message
> news:e4a9b19a-1b95-4df7-b6d9-e8c374bfb9c0@.a39g2000pre.googlegroups.com...
> On 3 dÃ©c, 18:04, dineshbabu.munug...@.gmail.com wrote:
> > On Dec 4, 3:42 am, pd...@.clic.net wrote:
> >
> > > I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server
> > > Standard.
> > > I have the switches /PAE /3GB in boot.ini
> >
> > > SQL max server memory is = 6656 MB
> >
> > > but with those settings I cannot get SQLServer to get more than 2.7 GB
> > > of RAM
> >
> > > If I use the AWE switch, then SQLServer can only use 128 MB max
> >
> > > What's wrong?
> >
> > > Paul
> >
> > Is it SQL Server 2000 or SQL Server 2005?
> > If its SQL Server 2000, then AWE is not supported
> > If its SQL Server 2005, then check the AWE 'Run Value' in
> > sp_configure... if its 0, then you might want to recycle the SQL
> > Server service to enable the AWE
> >
> > In any case i dont believe you need to have /3GB switch in boot.ini.
> SQL2005 Standard.
> Running in 32 bits system
> As soon as I use AWE, I'm stuck with 128 MB of RAM for SQL server...
> (i.e. I run dbcc checkDB so that it starts using rapidly memory and I
> see SQLServer.exe using not more than 128 MB of RAM in Task Manager).
> Paul
>
>|||Sorry. I missed that you are on SQL Server 2005.
In 32 -bit you do need AWE and as Ben pointed out gran permission Lock
Page in Memory permission to your service account.
To see if SQL server uses 6GB open PerfMonitor , do not use Task Manager
Visit also http://blogs.msdn.com/slavao/
<pdube@.clic.net> wrote in message
news:f9c9559b-d836-4b7f-92d4-bfc8834aab35@.s36g2000prg.googlegroups.com...
On 4 déc, 14:08, pd...@.clic.net wrote:
> On 4 déc, 10:45, "Uri Dimant" <u...@.iscar.co.il> wrote:
>
>
> > Hi
> > Do you have SP4 with hotfix?
> > Install hotfix from(http://support.microsoft.com/kb/899761)
> > Do you see in PerfMon that SQL Server allocate 6.6GB RAM?
> > <pd...@.clic.net> wrote in message
> >news:e4a9b19a-1b95-4df7-b6d9-e8c374bfb9c0@.a39g2000pre.googlegroups.com...
> > On 3 déc, 18:04, dineshbabu.munug...@.gmail.com wrote:
> > > On Dec 4, 3:42 am, pd...@.clic.net wrote:
> > > > I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server
> > > > Standard.
> > > > I have the switches /PAE /3GB in boot.ini
> > > > SQL max server memory is = 6656 MB
> > > > but with those settings I cannot get SQLServer to get more than 2.7
> > > > GB
> > > > of RAM
> > > > If I use the AWE switch, then SQLServer can only use 128 MB max
> > > > What's wrong?
> > > > Paul
> > > Is it SQL Server 2000 or SQL Server 2005?
> > > If its SQL Server 2000, then AWE is not supported
> > > If its SQL Server 2005, then check the AWE 'Run Value' in
> > > sp_configure... if its 0, then you might want to recycle the SQL
> > > Server service to enable the AWE
> > > In any case i dont believe you need to have /3GB switch in boot.ini.
> > SQL2005 Standard.
> > Running in 32 bits system
> > As soon as I use AWE, I'm stuck with 128 MB of RAM for SQL server...
> > (i.e. I run dbcc checkDB so that it starts using rapidly memory and I
> > see SQLServer.exe using not more than 128 MB of RAM in Task Manager).
> > Paul- Masquer le texte des messages précédents -
> > - Afficher le texte des messages précédents -
> SQL 2005 (9.00.3161.00)
> The hotfix is for SQL 2000...
> In PerfMon, I see Commited Bytes around 3.2 GB.
> In Task Manager I still see SQLServer.exe using 2.7 GB. I guess then
> that's just a problem related with Task Manager not showing the
> correct amount of RAM used...?
> Paul- Masquer le texte des messages précédents -
> - Afficher le texte des messages précédents -
When I say that I see 128 MB of RAM in SQLServer.exe when using AWE I
mean that's what I see in Task Manager. Am I correct looking at this
value?
Should I check PerfMon instead? Is the memory shown in TaskManager
only kernel memory and would not show all memory used by SQL?
Paul

8 GB of RAM

Thursday, March 8, 2012

64gb memory - recommendations, etc..

Multi proc server with 64gb memory.
Applications that use SQL Server 2000 & 2005 run on this system.
Can someone point me to a site / document / any material that has
information about best practices, recommendations, etc about configuring SQL
Server to use this much of memory ?
Cheers
sqlcatzHere are some items that you can use to shed light on the issues with large
memory.
Configuration -Memory, Large Memory Support Is Available in Windows 2000
(AWE)
http://www.support.microsoft.com/?id=283037
Configuration -Memory, SQL Server 7 & 2000 memory usage
http://www.support.microsoft.com/?id=321363
Configuration -Memory, SQL Server Memory
http://sqljunkies.com/Tutorial/0D4FF40A-695C-4327-A41B-F9F2FE2D58F6.scuk
Configuration -Memory, SQL Server to use more than 2 GB of physical memory
http://support.microsoft.com/kb/274750/
Configuration -Memory, Using AWE Memory
http://www.sql-server-performance.com/awe_memory.asp
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"SQLCatz" <SQLCatz@.discussions.microsoft.com> wrote in message
news:F7C8E4BB-39A2-4898-88B3-AC0BEA469E19@.microsoft.com...
> Multi proc server with 64gb memory.
> Applications that use SQL Server 2000 & 2005 run on this system.
> Can someone point me to a site / document / any material that has
> information about best practices, recommendations, etc about configuring
> SQL
> Server to use this much of memory ?
> Cheers
> sqlcatz
>

64gb memory - recommendations, etc..

Multi proc server with 64gb memory.
Applications that use SQL Server 2000 & 2005 run on this system.
Can someone point me to a site / document / any material that has
information about best practices, recommendations, etc about configuring SQL
Server to use this much of memory ?
Cheers
sqlcatz
Here are some items that you can use to shed light on the issues with large
memory.
Configuration -Memory, Large Memory Support Is Available in Windows 2000
(AWE)
http://www.support.microsoft.com/?id=283037
Configuration -Memory, SQL Server 7 & 2000 memory usage
http://www.support.microsoft.com/?id=321363
Configuration -Memory, SQL Server Memory
http://sqljunkies.com/Tutorial/0D4FF...2FE2D58F6.scuk
Configuration -Memory, SQL Server to use more than 2 GB of physical memory
http://support.microsoft.com/kb/274750/
Configuration -Memory, Using AWE Memory
http://www.sql-server-performance.com/awe_memory.asp
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"SQLCatz" <SQLCatz@.discussions.microsoft.com> wrote in message
news:F7C8E4BB-39A2-4898-88B3-AC0BEA469E19@.microsoft.com...
> Multi proc server with 64gb memory.
> Applications that use SQL Server 2000 & 2005 run on this system.
> Can someone point me to a site / document / any material that has
> information about best practices, recommendations, etc about configuring
> SQL
> Server to use this much of memory ?
> Cheers
> sqlcatz
>

64gb memory - recommendations, etc..

Multi proc server with 64gb memory.
Applications that use SQL Server 2000 & 2005 run on this system.
Can someone point me to a site / document / any material that has
information about best practices, recommendations, etc about configuring SQL
Server to use this much of memory ?
Cheers
sqlcatzHere are some items that you can use to shed light on the issues with large
memory.
Configuration -Memory, Large Memory Support Is Available in Windows 2000
(AWE)
http://www.support.microsoft.com/?id=283037
Configuration -Memory, SQL Server 7 & 2000 memory usage
http://www.support.microsoft.com/?id=321363
Configuration -Memory, SQL Server Memory
http://sqljunkies.com/Tutorial/0D4F...F2FE2D58F6.scuk
Configuration -Memory, SQL Server to use more than 2 GB of physical memory
http://support.microsoft.com/kb/274750/
Configuration -Memory, Using AWE Memory
http://www.sql-server-performance.com/awe_memory.asp
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"SQLCatz" <SQLCatz@.discussions.microsoft.com> wrote in message
news:F7C8E4BB-39A2-4898-88B3-AC0BEA469E19@.microsoft.com...
> Multi proc server with 64gb memory.
> Applications that use SQL Server 2000 & 2005 run on this system.
> Can someone point me to a site / document / any material that has
> information about best practices, recommendations, etc about configuring
> SQL
> Server to use this much of memory ?
> Cheers
> sqlcatz
>

64bit windows and 32bit SQL

I have a 64bit Windows Server machine running a 32bit version of SQL 2000
Standard. I am running into 'insufficient memory available' errors. I
upgraded the RAM from 4GB to 8GB, but the problem persists.
Do I need to use the /PAE or /3GB boot switch even though I am running a
64bit version of Windows? Do I need AWE setup for SQL to access more
memory?
I figure this has more to do with the 32 bit version of SQL not being able
to access all the memory. Any ideas?SQL 2000 Standard is limited to 2GB RAM.
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Marc Speed" <vw_marc@.hotmail.com> wrote in message
news:egONT2E$GHA.1220@.TK2MSFTNGP04.phx.gbl...
>I have a 64bit Windows Server machine running a 32bit version of SQL 2000
>Standard. I am running into 'insufficient memory available' errors. I
>upgraded the RAM from 4GB to 8GB, but the problem persists.
> Do I need to use the /PAE or /3GB boot switch even though I am running a
> 64bit version of Windows? Do I need AWE setup for SQL to access more
> memory?
> I figure this has more to do with the 32 bit version of SQL not being able
> to access all the memory. Any ideas?
>
>|||> I am running into 'insufficient memory available' errors.
Throwing more memory at the problem is probably not the solution. Have you
installed SP4? Do you get the error with only certain types of queries?
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Marc Speed" <vw_marc@.hotmail.com> wrote in message
news:egONT2E$GHA.1220@.TK2MSFTNGP04.phx.gbl...
>I have a 64bit Windows Server machine running a 32bit version of SQL 2000
>Standard. I am running into 'insufficient memory available' errors. I
>upgraded the RAM from 4GB to 8GB, but the problem persists.
> Do I need to use the /PAE or /3GB boot switch even though I am running a
> 64bit version of Windows? Do I need AWE setup for SQL to access more
> memory?
> I figure this has more to do with the 32 bit version of SQL not being able
> to access all the memory. Any ideas?
>
>

64bit windows and 32bit SQL

I have a 64bit Windows Server machine running a 32bit version of SQL 2000
Standard. I am running into 'insufficient memory available' errors. I
upgraded the RAM from 4GB to 8GB, but the problem persists.
Do I need to use the /PAE or /3GB boot switch even though I am running a
64bit version of Windows? Do I need AWE setup for SQL to access more
memory?
I figure this has more to do with the 32 bit version of SQL not being able
to access all the memory. Any ideas?SQL 2000 Standard is limited to 2GB RAM.
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Marc Speed" <vw_marc@.hotmail.com> wrote in message
news:egONT2E$GHA.1220@.TK2MSFTNGP04.phx.gbl...
>I have a 64bit Windows Server machine running a 32bit version of SQL 2000
>Standard. I am running into 'insufficient memory available' errors. I
>upgraded the RAM from 4GB to 8GB, but the problem persists.
> Do I need to use the /PAE or /3GB boot switch even though I am running a
> 64bit version of Windows? Do I need AWE setup for SQL to access more
> memory?
> I figure this has more to do with the 32 bit version of SQL not being able
> to access all the memory. Any ideas?
>
>|||> I am running into 'insufficient memory available' errors.
Throwing more memory at the problem is probably not the solution. Have you
installed SP4? Do you get the error with only certain types of queries?
Hope this helps.
Dan Guzman
SQL Server MVP
"Marc Speed" <vw_marc@.hotmail.com> wrote in message
news:egONT2E$GHA.1220@.TK2MSFTNGP04.phx.gbl...
>I have a 64bit Windows Server machine running a 32bit version of SQL 2000
>Standard. I am running into 'insufficient memory available' errors. I
>upgraded the RAM from 4GB to 8GB, but the problem persists.
> Do I need to use the /PAE or /3GB boot switch even though I am running a
> 64bit version of Windows? Do I need AWE setup for SQL to access more
> memory?
> I figure this has more to do with the 32 bit version of SQL not being able
> to access all the memory. Any ideas?
>
>

Saturday, February 25, 2012

64bit and performance counters

Based on my knowledge, it will be suitable for your 64bit SQL Server as you
could find the following information in the KB
The information in this article applies to:
Microsoft SQL Server 2000 (all editions) SP3
You could contact PSS as KB told to ask for a hotfix

If the hotfix
doesn't resolve your issue, your issue may be not share the same root cause
as fixed in KB: 812915. In this way, I will be glad to continue our
troubleshooting until it is resolved

Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||Are you sure that the Hotfix will work for 64bit?
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:YhgxzlmWEHA.3484@.cpmsftngxa10.phx.gbl...
> Hi Frankm,
> From your descriptions, I understood that you would like to the fix in
> KB:812915 will be possible for your performance counter issue. Have I
> understood you? If there is anything I misunderstood, please feel free to
> let me know

> Based on my knowledge, it will be suitable for your 64bit SQL Server as
you
> could find the following information in the KB
> ----
> The information in this article applies to:
> Microsoft SQL Server 2000 (all editions) SP3
> ----
> You could contact PSS as KB told to ask for a hotfix

If the hotfix
> doesn't resolve your issue, your issue may be not share the same root
cause
> as fixed in KB: 812915. In this way, I will be glad to continue our
> troubleshooting until it is resolved

>
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||Hi frankm,
I am sure that hotfix will work for 64bit SQL Server

Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||Thank you - I will attempt to apply the patch.
Thank you again ...
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:XE7dHSYXEHA.308@.cpmsftngxa10.phx.gbl...
> Hi frankm,
> I am sure that hotfix will work for 64bit SQL Server

> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||Thank you - I will attempt to apply the patch.
Thank you again ...
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:XE7dHSYXEHA.308@.cpmsftngxa10.phx.gbl...
> Hi frankm,
> I am sure that hotfix will work for 64bit SQL Server

> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||Hi Frankm,
Thanks for your prompt updates!
You could post back the result after applying the patches to Re-Open this
thread if the patch doesn't work for you. In this case, you issue might be
another root causes that has no relationship with KB: 812915 and it is
highly appreciated if you could create a new thread so that we could
troubleshooting this issue for you

Anyway, thanks for using MSDN Newsgroup! We are here to be of assistance
whenever you have problems!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

64bit and performance counters

Does anyone know if the hotfix mentioned in KB article 812915
[FIX: "Performance Monitor Shared Memory Setup Failed: -1" Error Message
When You Start SQL Server]
is the same for 64bit as for 32bit, my first guess is no - but I have to
ask.
We just installed 64bit SQL Server 2 weeks ago and now the performace
counters are gone and the above "-1" message shows up in the SQL Server
errolog. This looks exactly like the same problem we encountered with 32
bit.
Thanks,
FrankmHi Frankm,
From your descriptions, I understood that you would like to the fix in
KB:812915 will be possible for your performance counter issue. Have I
understood you? If there is anything I misunderstood, please feel free to
let me know:)
Based on my knowledge, it will be suitable for your 64bit SQL Server as you
could find the following information in the KB
----
The information in this article applies to:
Microsoft SQL Server 2000 (all editions) SP3
----
You could contact PSS as KB told to ask for a hotfix :) If the hotfix
doesn't resolve your issue, your issue may be not share the same root cause
as fixed in KB: 812915. In this way, I will be glad to continue our
troubleshooting until it is resolved :)
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Are you sure that the Hotfix will work for 64bit?
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:YhgxzlmWEHA.3484@.cpmsftngxa10.phx.gbl...
> Hi Frankm,
> From your descriptions, I understood that you would like to the fix in
> KB:812915 will be possible for your performance counter issue. Have I
> understood you? If there is anything I misunderstood, please feel free to
> let me know:)
> Based on my knowledge, it will be suitable for your 64bit SQL Server as
you
> could find the following information in the KB
> ----
> The information in this article applies to:
> Microsoft SQL Server 2000 (all editions) SP3
> ----
> You could contact PSS as KB told to ask for a hotfix :) If the hotfix
> doesn't resolve your issue, your issue may be not share the same root
cause
> as fixed in KB: 812915. In this way, I will be glad to continue our
> troubleshooting until it is resolved :)
>
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi frankm,
I am sure that hotfix will work for 64bit SQL Server :)
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Thank you - I will attempt to apply the patch.
Thank you again ...
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:XE7dHSYXEHA.308@.cpmsftngxa10.phx.gbl...
> Hi frankm,
> I am sure that hotfix will work for 64bit SQL Server :)
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi Frankm,
Thanks for your prompt updates!
You could post back the result after applying the patches to Re-Open this
thread if the patch doesn't work for you. In this case, you issue might be
another root causes that has no relationship with KB: 812915 and it is
highly appreciated if you could create a new thread so that we could
troubleshooting this issue for you :)
Anyway, thanks for using MSDN Newsgroup! We are here to be of assistance
whenever you have problems!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

64bit and performance counters

Based on my knowledge, it will be suitable for your 64bit SQL Server as you
could find the following information in the KB
----
The information in this article applies to:
Microsoft SQL Server 2000 (all editions) SP3
----
You could contact PSS as KB told to ask for a hotfix

If the hotfix
doesn't resolve your issue, your issue may be not share the same root cause
as fixed in KB: 812915. In this way, I will be glad to continue our
troubleshooting until it is resolved

Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Are you sure that the Hotfix will work for 64bit?
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messa
ge
news:YhgxzlmWEHA.3484@.cpmsftngxa10.phx.gbl...
> Hi Frankm,
> From your descriptions, I understood that you would like to the fix in
> KB:812915 will be possible for your performance counter issue. Have I
> understood you? If there is anything I misunderstood, please feel free to
> let me know

>
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi frankm,
I am sure that hotfix will work for 64bit SQL Server

Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Thank you - I will attempt to apply the patch.
Thank you again ...
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messa
ge
news:XE7dHSYXEHA.308@.cpmsftngxa10.phx.gbl...
> Hi frankm,
> I am sure that hotfix will work for 64bit SQL Server

> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi Frankm,
Thanks for your prompt updates!
You could post back the result after applying the patches to Re-Open this
thread if the patch doesn't work for you. In this case, you issue might be
another root causes that has no relationship with KB: 812915 and it is
highly appreciated if you could create a new thread so that we could
troubleshooting this issue for you

Anyway, thanks for using MSDN Newsgroup! We are here to be of assistance
whenever you have problems!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

64 bit SQL 2005 memory problem

Large Query immediately eats up all available memory in Server 2003 Server
XP1 SQL 2005 64 bit (8 gig ram). CPU pegs at 99% and nothing else appears to
be able to access SQL Server. Query is attempting to delete possibly as many
as 200 million duplicate entries in a table. Do settings exist in SQL to
limit the amount of processing power any one query can tap into from the
server?
Regards,
Jamie
Hi
Why do you try to delete 200 million rows at one transaction?
Can you divide it to small tranasctions and then perfom deletion?
SET ROWCOUNT 1000
WHILE 1 = 1
BEGIN
DELETE statement Here
IF @.@.ROWCOUNT = 0
BEGIN
BREAK
END
ELSE
BEGIN
CHECKPOINT --or even BACKUP LOG file
END
END
SET ROWCOUNT 0
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:B566306D-F6DC-4CB5-B85A-E0978B158495@.microsoft.com...
> Large Query immediately eats up all available memory in Server 2003 Server
> XP1 SQL 2005 64 bit (8 gig ram). CPU pegs at 99% and nothing else appears
> to
> be able to access SQL Server. Query is attempting to delete possibly as
> many
> as 200 million duplicate entries in a table. Do settings exist in SQL to
> limit the amount of processing power any one query can tap into from the
> server?
> --
> Regards,
> Jamie
|||First i would run this query when nobody is connected to avoid locks etc..
Second if possible split the query in steps instead of doing all deletes in
1 time.
Example...do 1000 deletes atime and so on.
You can set the minimal query memory at the server level, i have no
experience with changing this option .
Good luck.
DBA4ever
"thejamie" wrote:

> Large Query immediately eats up all available memory in Server 2003 Server
> XP1 SQL 2005 64 bit (8 gig ram). CPU pegs at 99% and nothing else appears to
> be able to access SQL Server. Query is attempting to delete possibly as many
> as 200 million duplicate entries in a table. Do settings exist in SQL to
> limit the amount of processing power any one query can tap into from the
> server?
> --
> Regards,
> Jamie
|||Can I point this in another directions? There is something called AWE that
is used to allocate memory and it appears that min and max memory can be
set... in the memory section of the server properties. How will this effect
such a query.
I should have added that this is the only query running on the server and it
is simply a test of what happens under severe conditions. The test indicates
to me that the server memory should be tempered. After the query ran 8
hours, I canceled it. It locked up the server last night and we had to do a
cold boot. In my opinion, despite the recklessness of the delete statement,
a cold boot should rarely if ever be required as the solution to a SQL
problem arising from a mis-directed query.
Regards,
Jamie
"Hate_orphaned_users" wrote:
[vbcol=seagreen]
> First i would run this query when nobody is connected to avoid locks etc..
> Second if possible split the query in steps instead of doing all deletes in
> 1 time.
> Example...do 1000 deletes atime and so on.
> You can set the minimal query memory at the server level, i have no
> experience with changing this option .
> Good luck.
> DBA4ever
> "thejamie" wrote:
|||On Thu, 7 Dec 2006 05:20:01 -0800, thejamie
<thejamie@.discussions.microsoft.com> wrote:

>There is something called AWE that
>is used to allocate memory
AWE is for 32-bit, it does not apply to 64-bit SQL Server.
Roy Harvey
Beacon Falls, CT
|||On Thu, 7 Dec 2006 05:20:01 -0800, thejamie
<thejamie@.discussions.microsoft.com> wrote:

> After the query ran 8
>hours, I canceled it. It locked up the server last night and we had to do a
>cold boot. In my opinion, despite the recklessness of the delete statement,
>a cold boot should rarely if ever be required as the solution to a SQL
>problem arising from a mis-directed query.
The normal run time for a query that deletes 200 million rows may very
well exceed 8 hours. When such a query is cancelled while running, it
can take longer to toll back the work already done that it took to do
it in the first place, so 12 hours rolling back 8 hours of processing
would not be unexpected.
Roy Harvey
Beacon Falls, CT
|||You should select the "Dynamically configure SQL server memory" option.
Then set the Maximum option to full.
|||> Thanks for that information, Dan. That's what I get for going by the
> documentation! 8-)
I understand, Roy. I was under the same impression until I ran across
Slova's blog.
Hope this helps.
Dan Guzman
SQL Server MVP
"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:g97gn2hckaq1h4um92i784tc7kpku4vitk@.4ax.com...
> On Thu, 7 Dec 2006 07:45:20 -0600, "Dan Guzman"
> <guzmanda@.nospam-online.sbcglobal.net> wrote:
>
> Thanks for that information, Dan. That's what I get for going by the
> documentation! 8-)
> "3 Note that the sp_configure awe enabled option is present on 64-bit
> SQL Server, but it is ignored. It is subject to removal in future
> releases or service packs of 64-bit SQL Server."
> Roy
|||How about the lightweight pooling with Windows fibers? Should Boost SQL
Server priority be checked or unchecked? Should worker threads be set for 0?
Regards,
Jamie
"Roy Harvey" wrote:

> On Thu, 7 Dec 2006 05:20:01 -0800, thejamie
> <thejamie@.discussions.microsoft.com> wrote:
>
> AWE is for 32-bit, it does not apply to 64-bit SQL Server.
> Roy Harvey
> Beacon Falls, CT
>
|||The service was restarted and this had no effect on the memory and cpu
usage... the cold boot came next, now the cpu usage and memory are maxed out
again.
Regards,
Jamie
"Dan Guzman" wrote:

> I understand, Roy. I was under the same impression until I ran across
> Slova's blog.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Roy Harvey" <roy_harvey@.snet.net> wrote in message
> news:g97gn2hckaq1h4um92i784tc7kpku4vitk@.4ax.com...
>

64 bit SQL 2005 memory problem

Large Query immediately eats up all available memory in Server 2003 Server
XP1 SQL 2005 64 bit (8 gig ram). CPU pegs at 99% and nothing else appears t
o
be able to access SQL Server. Query is attempting to delete possibly as man
y
as 200 million duplicate entries in a table. Do settings exist in SQL to
limit the amount of processing power any one query can tap into from the
server?
--
Regards,
JamieHi
Why do you try to delete 200 million rows at one transaction?
Can you divide it to small tranasctions and then perfom deletion?
SET ROWCOUNT 1000
WHILE 1 = 1
BEGIN
DELETE statement Here
IF @.@.ROWCOUNT = 0
BEGIN
BREAK
END
ELSE
BEGIN
CHECKPOINT --or even BACKUP LOG file
END
END
SET ROWCOUNT 0
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:B566306D-F6DC-4CB5-B85A-E0978B158495@.microsoft.com...
> Large Query immediately eats up all available memory in Server 2003 Server
> XP1 SQL 2005 64 bit (8 gig ram). CPU pegs at 99% and nothing else appears
> to
> be able to access SQL Server. Query is attempting to delete possibly as
> many
> as 200 million duplicate entries in a table. Do settings exist in SQL to
> limit the amount of processing power any one query can tap into from the
> server?
> --
> Regards,
> Jamie|||First i would run this query when nobody is connected to avoid locks etc..
Second if possible split the query in steps instead of doing all deletes in
1 time.
Example...do 1000 deletes atime and so on.
You can set the minimal query memory at the server level, i have no
experience with changing this option .
Good luck.
DBA4ever
"thejamie" wrote:

> Large Query immediately eats up all available memory in Server 2003 Server
> XP1 SQL 2005 64 bit (8 gig ram). CPU pegs at 99% and nothing else appears
to
> be able to access SQL Server. Query is attempting to delete possibly as m
any
> as 200 million duplicate entries in a table. Do settings exist in SQL to
> limit the amount of processing power any one query can tap into from the
> server?
> --
> Regards,
> Jamie|||Can I point this in another directions? There is something called AWE that
is used to allocate memory and it appears that min and max memory can be
set... in the memory section of the server properties. How will this effect
such a query.
I should have added that this is the only query running on the server and it
is simply a test of what happens under severe conditions. The test indicate
s
to me that the server memory should be tempered. After the query ran 8
hours, I canceled it. It locked up the server last night and we had to do a
cold boot. In my opinion, despite the recklessness of the delete statement
,
a cold boot should rarely if ever be required as the solution to a SQL
problem arising from a mis-directed query.
--
Regards,
Jamie
"Hate_orphaned_users" wrote:
[vbcol=seagreen]
> First i would run this query when nobody is connected to avoid locks etc..
> Second if possible split the query in steps instead of doing all deletes i
n
> 1 time.
> Example...do 1000 deletes atime and so on.
> You can set the minimal query memory at the server level, i have no
> experience with changing this option .
> Good luck.
> DBA4ever
> "thejamie" wrote:
>|||On Thu, 7 Dec 2006 05:20:01 -0800, thejamie
<thejamie@.discussions.microsoft.com> wrote:

>There is something called AWE that
>is used to allocate memory
AWE is for 32-bit, it does not apply to 64-bit SQL Server.
Roy Harvey
Beacon Falls, CT|||On Thu, 7 Dec 2006 05:20:01 -0800, thejamie
<thejamie@.discussions.microsoft.com> wrote:

> After the query ran 8
>hours, I canceled it. It locked up the server last night and we had to do
a
>cold boot. In my opinion, despite the recklessness of the delete statemen
t,
>a cold boot should rarely if ever be required as the solution to a SQL
>problem arising from a mis-directed query.
The normal run time for a query that deletes 200 million rows may very
well exceed 8 hours. When such a query is cancelled while running, it
can take longer to toll back the work already done that it took to do
it in the first place, so 12 hours rolling back 8 hours of processing
would not be unexpected.
Roy Harvey
Beacon Falls, CT|||> Thanks for that information, Dan. That's what I get for going by the
> documentation! 8-)
I understand, Roy. I was under the same impression until I ran across
Slova's blog.
Hope this helps.
Dan Guzman
SQL Server MVP
"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:g97gn2hckaq1h4um92i784tc7kpku4vitk@.
4ax.com...
> On Thu, 7 Dec 2006 07:45:20 -0600, "Dan Guzman"
> <guzmanda@.nospam-online.sbcglobal.net> wrote:
>
> Thanks for that information, Dan. That's what I get for going by the
> documentation! 8-)
> "3 Note that the sp_configure awe enabled option is present on 64-bit
> SQL Server, but it is ignored. It is subject to removal in future
> releases or service packs of 64-bit SQL Server."
> Roy|||How about the lightweight pooling with Windows fibers? Should Boost SQL
Server priority be checked or unchecked? Should worker threads be set for
0?
--
Regards,
Jamie
"Roy Harvey" wrote:

> On Thu, 7 Dec 2006 05:20:01 -0800, thejamie
> <thejamie@.discussions.microsoft.com> wrote:
>
> AWE is for 32-bit, it does not apply to 64-bit SQL Server.
> Roy Harvey
> Beacon Falls, CT
>|||The service was restarted and this had no effect on the memory and cpu
usage... the cold boot came next, now the cpu usage and memory are maxed out
again.
--
Regards,
Jamie
"Dan Guzman" wrote:

> I understand, Roy. I was under the same impression until I ran across
> Slova's blog.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Roy Harvey" <roy_harvey@.snet.net> wrote in message
> news:g97gn2hckaq1h4um92i784tc7kpku4vitk@.
4ax.com...
>|||Thanks Hate_Orphaned_Users,
This may be the answer I am looking for. In the meantime, before I can
check this the server may need another cold boot. Will let you know.
--
Regards,
Jamie
"Hate_orphaned_users" wrote:

> You should select the "Dynamically configure SQL server memory" option.
> Then set the Maximum option to full.
>
>
>

Friday, February 24, 2012

64 bit memory and AWE ?

Hi There

I have installed 64 bit Standard Edition SS 2005 on a 64 bit WOndows Server 2003 R2 platform.

When i go to Memory setting for this instance i set max server memory to 6 Gig.

I am presuming i do not have to enable AWE, sicne everything is 64 bit.

Is this correct ?

Thanx

AWE is used for 32-bit OS due to 32-bit system can only address 4GB memory in conventual way, so it need to set /PAE in boot.ini file and set AWE enabled in SQL server.

but for 64-bit OS and SQL server (both 2000 and 2005) do not need to set this option.

64 bit memory and AWE ?

Hi There

I have installed 64 bit Standard Edition SS 2005 on a 64 bit WOndows Server 2003 R2 platform.

When i go to Memory setting for this instance i set max server memory to 6 Gig.

I am presuming i do not have to enable AWE, sicne everything is 64 bit.

Is this correct ?

Thanx

AWE is used for 32-bit OS due to 32-bit system can only address 4GB memory in conventual way, so it need to set /PAE in boot.ini file and set AWE enabled in SQL server.

but for 64-bit OS and SQL server (both 2000 and 2005) do not need to set this option.

Monday, March 19, 2012

9GB log file generated

8GB memory installation

8GB memory installation

8GB memory installation

Sunday, March 11, 2012

80004005 ODBC SQL Server Driver shared memory or TCP/IP sockets er

8 GB of RAM

8 GB of RAM

8 GB of RAM

Thursday, March 8, 2012

64gb memory - recommendations, etc..

64gb memory - recommendations, etc..

64gb memory - recommendations, etc..

64bit windows and 32bit SQL

64bit windows and 32bit SQL

Saturday, February 25, 2012

64bit and performance counters

64bit and performance counters

64bit and performance counters

64 bit SQL 2005 memory problem

64 bit SQL 2005 memory problem

Friday, February 24, 2012

64 bit memory and AWE ?

64 bit memory and AWE ?

3G ram for SQL server

Blog Archive

About Me