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
May 25 2007- From the snippet of Tibor Karaszi , SQL Server MVP I have raised a feedback form on Connect.Microsoft website to get newer version (SQL Server 2005) about Index Defragmentation Best practices information. Vote your interest to get newer documentation quickly for most of our benefit to attain...
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