I want know about changing the memory and Cpu value on the fly and generally on instance level.
Actually i want to manage the multiple instances.
View Complete Post
This is the server information:
SQL Server 2005 -- Standard Edition --64 bit --64 bit OS
RAM - 8 GB -- 8 processors
SQL Server is using 4 GB of RAM ...
1. We are expecting that there is more RAM space , that the SQL Server can utilize ... What and all options that I need to change ..
2. what are the best practices on this environment fot effectively utilizing the server resources.
Since it is a 64 bit sql server, enabling AWE is not usefull .. any suggestions highly appreciated.
We are attempting to change the default collation of an SQL Server 2005 Clustered environment. We have created an "unattended install" script to perform this, and have modified it several times as errors have arisen repeatedly. The last time, however, we
used the following script:
start /wait setup.exe /qb VS=<FQN of SQL Server Virtual Name> INSTANCENAME=MSSQLSERVER REINSTALL=SQL_Engine REBUILDDATABASE=1 ADMINPASSWORD=<adminpwd> SAPWD=<NEW sa pwd> SQLCOLLATION=SQL_Latin1_General_CP1_CI_AS SQLACCOUNT=<domain\user>
SQLPASSWORD=<pwd> AGTACCOUNT=<domain\user> AGTPASSWORD=pwd GROUP=SQL Group REINSTALLMODE=vomus
We are running this script from the primary (Active) node of the cluster. We did notice that the bootstrap logs created from this final execution did include logs from both nodes. When I look in the Summary.txt file, it tells me that Setup succeeded with
the installation. After the script executed, we rolled the cluster from primary to secondary, and rebooted the primary node. We then rolled the cluster back to the primary, and rebooted the secondary node. Once that was complete, we cycled the SQL Server service
from the SQL Configuration Manager. After all those steps, we opened SSMS client to look at the properties of master, and the collation was still CI_AI.
We are losing valuable time in
I am running a huge SSRS 2008 report and it gets rendered sometimes and sometimes it gives me an error,
"The report execution has expired or cannot be found. (rsExecutionNotFound)”.
When I see SQL Server log after this issue comes I see following message there;
"A significant part of sql server memory has been paged out. This may result in performance degradation. Duration: 300 seconds. Working set(KB): 97672, memory utilization 42%"
Please help me to know what is the issue and how to fix it.
We are running SQL Server 2008 R2 on on Window Server 2008 (x64).
Once in every 2 weeks we end up restarting the SQL Server, due to Physical Memory keep growing.
Is there a good way to pinpoint the problem what cause this Physical Memory to grow?
We have a situation where one of our customers is running Windows 2003 Enterprise Edition 32bit with 8 GBs of physical RAM. Upgrading to Windows Server 2008 64bit is not an immediate option (although I wish it were). All the documentation about SQL Server
2008 Workgroup edition indicates that the new version will address 4 GBs of memory however it does not distinguish between 32bit vs 64bit.
Previously we have run SQL Workgroup 2005 under Windows 2003 and have applied the /3gb switch in boot.ini to get SQL to recognize the maximum amount of memory possible. Now that we are using SQL 2008 with the /pae switch, do we need to still specify the
/3gb switch or can SQL 2008 32bit actually see more than the 3GBs and address 4? I haven't been able to find any information on this configuration.