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
Fragmentation is dearest friend of database when you need to deal with Performance, so by using the DBCC statements and other methods here you can deal the database level fragmentation, what about the physical level fragmentation? So what is the best way forward to fix the data file fragmentation in...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
03-26-2008
Filed under: sql server, performance, blogs, dbcc, disk space, object, file, best practice, monitoring, showcontig, defrag, diskkeeper
The message on subject is self-explanatory where your disk subsystem is referring to SQL Server that it is unable to cope up the demand. Having AUTOGROW option enabled on a SQL Server database is a common setup that allows SQL Server automatically expands the database when additional space is required...
One of the best features you have in the SQL Server is to create database data file (additional) on fly without having a slow performance affect on existing connections. But think about how SQL Server manages to use server threads for the data file that is used for the databases and how big disk queue...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
01-29-2008
Filed under: sql server, performance, management, indexes, windows, i/o, sysmon, disk space, usage, resource, perflib, worker threads, task manager
Whenever the SQL Server is struggling to write the transactions to the disk, you would observe WRITELOG wait type within SP_WHO2 results. So when you observer such wait types then you should be worried on the disks performance, either you plan for shrinking the transaction log (which is a temporary workaround...
Are you watching your disk space during the indexes operations where these database objects are stored? Recently I was stumped on a database that is only 5GB had reindexing process failure due to 10% of disk free space was available. For your information you need to consider that one of the reason behind...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
09-28-2007
Filed under: sql server, performance, indexes, dba, optimization, disk space, best practice, hardware, disks, sorting, reindexing