You may be aware that or seen within your Database platform about slower disk performance than expect having multiple disks in Windows Server 2003 environment when you use a hardware-based redundant array of independent disks (RAID) or a software-based RAID. This could be due to one of the reasons such...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
04-28-2008
Filed under: sql server, performance, microsoft, technet, i/o, article, disk, best practices, monitoring, deployment, layout
Have you ever wondered about flushing databases? Well not quite possible to flush it straight away and not a best practice too on the live server, so what it is about and you need to know about transactions state when they occur. Say when the changes occur in a database the changes are formed as transactions...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
04-22-2008
Filed under: sql server, performance, msdn, backup, blogs, database, transaction log, cache, i/o, flush, monitoring, checkpointl
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
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
It is a good practice to determine the required capacity for a database application before it is deployed on the Production environment. As it speaks the I/O system is "most" important to the performance of SQL Server, in the event of any performance loss or even configuring a new server for...
When it comes to resolving table fragmentation, the basic checkout you perform is to run DBCC INDEXDEFRAG or even run DBCC DBREINDEX statements. As per the default configuraiton SQL Database Engine allocates a new extent to an allocation unit only when it cannot quickly find a page in an existing extent...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
09-04-2007
Filed under: sql server, performance, indexes, data, i/o, table, insert, allocation, fragmentation, deadlock, extent
When you run normal SELECT statement from the Activity Monitor, the session has a status of "suspended", a command of "SELECT" and a wait type of "ASYNC_NETWORK_IO". What do you expect to the see the results and within the column status, we will see quite a few requests...
Dynamic Management Views (DMV) are very useful to get server state information to monitor the status, but not always you have to still continue in monitoring using SYSMON & PROFILER that are available by default with SQL installation. The engine within SQL Server 2005 improves accuracy by using the...