Comments for Ajmer Dhariwal's SQL Server blog http://www.eraofdata.com/blog SQL Server posts that DBAs will (hopefully) find useful. Fri, 30 Jul 2010 16:36:33 +0000 http://wordpress.org/?v=2.6.1 Comment on SQL Server memory configuration by Ajmer Dhariwal http://www.eraofdata.com/blog/2008/10/sql-server-memory-configuration/#comment-2459 Ajmer Dhariwal Tue, 08 Jun 2010 22:03:50 +0000 http://www.eraofdata.com/blog/?p=3#comment-2459 That looks about right to me. Monitoring the buffer cache size via the perfmon counters should validate those settings by showing memory usage eventually growing to 6GB and staying at that limit. That looks about right to me. Monitoring the buffer cache size via the perfmon counters should validate those settings by showing memory usage eventually growing to 6GB and staying at that limit.

]]> Comment on SQL Server memory configuration by T_Brothers http://www.eraofdata.com/blog/2008/10/sql-server-memory-configuration/#comment-2458 T_Brothers Tue, 08 Jun 2010 20:57:02 +0000 http://www.eraofdata.com/blog/?p=3#comment-2458 Great post! Thanks! We have a Windows 2003 Ent server 64-bit with 8GB RAM. We are running SQL 2005 Ent 32-bit. We do not have /PAE or /3GB in the boot.ini and I will not add either of them. I will enable AWE wirthin SQL and set max memory to 6GB. I will enable "locked pages in memory" in gpedit.msc Then I will reboot the server and hope for the best. Does that sound correct? Thanks, T_Brothers Great post! Thanks!

We have a Windows 2003 Ent server 64-bit with 8GB RAM.
We are running SQL 2005 Ent 32-bit.

We do not have /PAE or /3GB in the boot.ini and I will not add either of them.
I will enable AWE wirthin SQL and set max memory to 6GB.
I will enable “locked pages in memory” in gpedit.msc
Then I will reboot the server and hope for the best.

Does that sound correct?

Thanks,
T_Brothers

]]> Comment on Identifying the source of SQL Server login failures (18456 errors) by Rick Morgan http://www.eraofdata.com/blog/2009/01/loginfailures/#comment-2457 Rick Morgan Sat, 05 Jun 2010 23:10:48 +0000 http://www.eraofdata.com/blog/?p=114#comment-2457 Very informative and helpful - save me from utter frustration. Thanks for the work. Very informative and helpful - save me from utter frustration. Thanks for the work.

]]> Comment on SQL Server memory configuration by T Jacobs http://www.eraofdata.com/blog/2008/10/sql-server-memory-configuration/#comment-2456 T Jacobs Mon, 03 May 2010 10:39:16 +0000 http://www.eraofdata.com/blog/?p=3#comment-2456 Thanks. That was a big help Thanks. That was a big help

]]> Comment on SQL Server memory configuration by Ajmer Dhariwal http://www.eraofdata.com/blog/2008/10/sql-server-memory-configuration/#comment-2455 Ajmer Dhariwal Thu, 29 Apr 2010 19:24:21 +0000 http://www.eraofdata.com/blog/?p=3#comment-2455 Thanks. You shouldn't have to enable PAE, but if it's 32-bit SQL you'll need to enable awe and because of that set a cap on memory usage, as it will use all the memory that edition can access. Thanks. You shouldn’t have to enable PAE, but if it’s 32-bit SQL you’ll need to enable awe and because of that set a cap on memory usage, as it will use all the memory that edition can access.

]]> Comment on SQL Server memory configuration by T Jacobs http://www.eraofdata.com/blog/2008/10/sql-server-memory-configuration/#comment-2454 T Jacobs Thu, 29 Apr 2010 17:37:31 +0000 http://www.eraofdata.com/blog/?p=3#comment-2454 Hi Ajmer, This is a great post. I just to to resolve one final lingering in our mind. We are porting(until our sql 2008 is ready) our 32 bit SQL 2000 SP3 server (production version) to a 64 bit machine with 64 gig of ram with databases on a SAN. Based on the that there should be no PAE in the boot.ini. Correct? AWE should be disable. Correct? No max memory set. Correct? SQL 2000 with use all available ram. Correct? Thanks in Advance Hi Ajmer,

This is a great post. I just to to resolve one final lingering in our mind. We are porting(until our sql 2008 is ready) our 32 bit SQL 2000 SP3 server (production version) to
a 64 bit machine with 64 gig of ram with databases on a SAN. Based on the that there should be no PAE in the boot.ini. Correct?
AWE should be disable. Correct?
No max memory set. Correct?
SQL 2000 with use all available ram. Correct?

Thanks in Advance

]]> Comment on Misaligned disk partition offsets and SQL Server Performance by SQL Server and Disk IO | Ajmer Dhariwal's SQL Server blog http://www.eraofdata.com/blog/2010/02/misaligned-disk-partition-offsets-and-sql-server-performance/#comment-2451 SQL Server and Disk IO | Ajmer Dhariwal's SQL Server blog Tue, 09 Feb 2010 20:09:02 +0000 http://www.eraofdata.com/blog/?p=221#comment-2451 [...] of Data home || about || contact || blog || « The SQL Server default trace Misaligned disk partition offsets and SQL Server Performance [...] [...] of Data home || about || contact || blog || « The SQL Server default trace Misaligned disk partition offsets and SQL Server Performance [...]

]]> Comment on SQL Server memory configuration by Ajmer Dhariwal http://www.eraofdata.com/blog/2008/10/sql-server-memory-configuration/#comment-2450 Ajmer Dhariwal Mon, 08 Feb 2010 09:03:07 +0000 http://www.eraofdata.com/blog/?p=3#comment-2450 Hi Jignesh, As indicatd in the blog, if no memory limits are set then SQL Server can eventually use up as much memory as it possibly can, if the workload is there. On a 32-bit system (without awe enabled) this will be @ 1.6 GB. There can be many reasons for the sluggish behaviour - how much RAM is there in total on the machine? If SQL Server is using most of what is available this may be a factor. Otherwise narrow down what is causing the issue using http://technet.microsoft.com/en-gb/library/cc966540.aspx Regards, Ajmer Hi Jignesh,

As indicatd in the blog, if no memory limits are set then SQL Server can eventually use up as much memory as it possibly can, if the workload is there. On a 32-bit system (without awe enabled) this will be @ 1.6 GB.
There can be many reasons for the sluggish behaviour - how much RAM is there in total on the machine? If SQL Server is using most of what is available this may be a factor.
Otherwise narrow down what is causing the issue using http://technet.microsoft.com/en-gb/library/cc966540.aspx

Regards,
Ajmer

]]> Comment on SQL Server memory configuration by Jignesh http://www.eraofdata.com/blog/2008/10/sql-server-memory-configuration/#comment-2449 Jignesh Fri, 05 Feb 2010 08:12:48 +0000 http://www.eraofdata.com/blog/?p=3#comment-2449 Hi Thanks for the blog, i wanted to know is there any way that SQL server process release unused memory my problem is we have a single instance server containing a signle database to which atleast 10 users are conneted at a time now this SQL server process start consuming memory upto 1.5GB in no time and it resonses slow back to the client machines can you have any sugesion on this Hi
Thanks for the blog,

i wanted to know is there any way that SQL server process release unused memory
my problem is we have a single instance server containing a signle database to which atleast 10 users are conneted at a time

now this SQL server process start consuming memory upto 1.5GB in no time and it resonses slow back to the client machines

can you have any sugesion on this

]]> Comment on Orphaned MSDTC transactions (-2 spids) by Mike http://www.eraofdata.com/blog/2008/12/orphaned-msdtc-transactions-2-spids/#comment-2448 Mike Wed, 16 Dec 2009 05:51:33 +0000 http://www.eraofdata.com/blog/?p=99#comment-2448 Thanks for your suggestion. The GUI MSDTC actually matched what the queries showed i.e. killing the SPID also removed it from the GUI. Restarting the MSDTC didn't work but restarting the SQL Server Service ended up fixing the issue. Thanks for your suggestion. The GUI MSDTC actually matched what the queries showed i.e. killing the SPID also removed it from the GUI. Restarting the MSDTC didn’t work but restarting the SQL Server Service ended up fixing the issue.

]]>