Memory - an important aspect of system performance within a RDBMS platform, not specific to a database product or application. Coming to Microsoft related products such as Windows Server and SQL Server so on, various resources available on web such as MSDN blogs, Books Online and articles, frequently...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
04-01-2008
Filed under: sql server, performance, memory, cache, disk space, troubleshoot, system, best practice, raid, hardware, monitoring, configuration, baseline
Have you seen the above message within the SQL Server error logs? If not then no need to worry and make sure to continue your performance monitoring tasks. So when to be concerned! It is evident that SQL Server 2005 component handles memory differently as compared to SQL Server 2000 version. As one of...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
03-07-2008
Filed under: sql server, performance, memory, dmv, windows, 2000, 2005, awe, 64 bit, monitoring, worker threads, paging out, buffers, verison
Bottlenecks aka locking & blocking is a quite common scenario within a RDBMS platform, that too SQL Server is not an exception at all. With an access to shared resources causes bottlenecks and demands on shared resources cause poor response time and must be identified and tuned. Few root causes for...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
02-25-2008
Filed under: sql server, performance, memory, dba, i/o, disk, 2008, development, cpu, best practice, capture, resource governor
Recently I have to search for the information on the total size of free physical memory on the SQL Server which is causing lots of performance issues, when reported to CSS they have supplied the following TSQL to get more information in this regard: With VASummary(Size,Reserved,Free) AS (SELECT Size...
This may be last post in Performance Tuning & Security blog section here for this year!! Most of this year in the forums & newsgroups I have seen a common question asking about memory configuration within SQL Server 2005. As you may be aware that SQL Server 2005 (onwards) the memory allocation...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
12-28-2007
Filed under: sql server, performance, memory, security, applications, best practice, awe, pae, dynamic, 3gb, benchmarking, performance monitoring, settings
Got an email to inbox asking a resolution for : I can't find a remedy for this problem on Google either. Any help would be appreciated. When performing the data mining cube process - Error: Memory error: Allocation failure : Not enough storage is available to process this command. For the error text...
Yet another AWE memory settings blog post here that I'm posting for the issues we have had recently. Before going into details review about 3GBPAE blurb here and also refer to this KBA274750 to enable more than 2GB memory within your SQL Server Enterprise edition instance. Coming to the problem on...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
08-23-2007
Filed under: sql server, performance, memory, security, windows, edition, enterprise, instances, awe, pae, 3gb
The system DMV sys.dm_os_schedulers is an useful DMV to find such as running tasks & active workers threads etc. This is required to monitor the system state is heavily loaded or not, in particular this view will help you identify if there is any CPU bottleneck in the SQL Server machine. SELECT scheduler_id...
Is 64 bit means more memory? Yes, to be precise. Microsoft has been investing heavily on X64 bit and within couple of years there will be no more development on 32-bit applications, as per the recent road map. So within 32-bit application it is one of the reason that memory has been a constraint on scaling...
As usual for every performance issue there are many considerations that need to be evaluated when determining how to investigate the root cause for slower performance of many SQL Server databases. I would suggest that an important consideration is whether to use a 64-bit platform or a 32-bit platform...