Very Computer

> Steven, if the database file itself is fragmented and spread all over the
> disk, then an operating system level defrag is okay (while SQL Server is
> stopped). Then start the SQL Server service, and rebuild your clustered
> indexes, to make sure there's no fragmentation within the clustered
indexes.

> In general, if you create your database files large enough in the
beginning,
> they don't grow afterwards, and that helps in keeping the complete file
> together at the OS level. In that case, a clustered index rebuild is good
> enough, especially when your queries perform large index scans.
> --
> HTH,
> Vyas, MVP (SQL Server)

> http://vyaskn.tripod.com/

> Is using a disk defrag utility on a SQL server .DAT device
> file OK?

> I cannot imagine this is OK, yet can find nothing at
> Microsoft saying so. They do have have bad stuff to say
> about using NTFS Compression.  I was in a meeting on
> Thursday, and MS Consulting was telling a customer this
> was OK.

> Imagine I create a clustered index on a table on this
> device.  Correct me if I am wrong, but isn't a clustered
> index about the physical organization of data pages on the
> disk, for fast sequential reads?  Wouldn't using a disk
> defrag utility (of course shutting down SQL Server so the
> file is not in use) blow SQL Server's mind as data pages
> are moved underneath it?

> Thanks

> Hi Vyas,

> How does one rebuild the indexes the easiest way?

> Thanks
> Andrew

> > Steven, if the database file itself is fragmented and spread all over
the
> > disk, then an operating system level defrag is okay (while SQL Server is
> > stopped). Then start the SQL Server service, and rebuild your clustered
> > indexes, to make sure there's no fragmentation within the clustered
> indexes.

> > In general, if you create your database files large enough in the
> beginning,
> > they don't grow afterwards, and that helps in keeping the complete file
> > together at the OS level. In that case, a clustered index rebuild is
good
> > enough, especially when your queries perform large index scans.
> > --
> > HTH,
> > Vyas, MVP (SQL Server)

> > http://vyaskn.tripod.com/

> > Is using a disk defrag utility on a SQL server .DAT device
> > file OK?

> > I cannot imagine this is OK, yet can find nothing at
> > Microsoft saying so. They do have have bad stuff to say
> > about using NTFS Compression.  I was in a meeting on
> > Thursday, and MS Consulting was telling a customer this
> > was OK.

> > Imagine I create a clustered index on a table on this
> > device.  Correct me if I am wrong, but isn't a clustered
> > index about the physical organization of data pages on the
> > disk, for fast sequential reads?  Wouldn't using a disk
> > defrag utility (of course shutting down SQL Server so the
> > file is not in use) blow SQL Server's mind as data pages
> > are moved underneath it?

> > Thanks

> Andrew,

> Check out the section "DBCC DBREINDEX (T-SQL)" in the SQL Server 7.0 Books
> Online.

> -------------------------------------------
> BP Margolin
> Please reply only to the newsgroups.
> When posting, inclusion of SQL (CREATE TABLE ..., INSERT ..., etc.) which
> can be cut and pasted into Query Analyzer is appreciated.

> > Hi Vyas,

> > How does one rebuild the indexes the easiest way?

> > Thanks
> > Andrew

> > > Steven, if the database file itself is fragmented and spread all over
> the
> > > disk, then an operating system level defrag is okay (while SQL Server
is
> > > stopped). Then start the SQL Server service, and rebuild your
clustered
> > > indexes, to make sure there's no fragmentation within the clustered
> > indexes.

> > > In general, if you create your database files large enough in the
> > beginning,
> > > they don't grow afterwards, and that helps in keeping the complete
file
> > > together at the OS level. In that case, a clustered index rebuild is
> good
> > > enough, especially when your queries perform large index scans.
> > > --
> > > HTH,
> > > Vyas, MVP (SQL Server)

> > > http://vyaskn.tripod.com/

> > > Is using a disk defrag utility on a SQL server .DAT device
> > > file OK?

> > > I cannot imagine this is OK, yet can find nothing at
> > > Microsoft saying so. They do have have bad stuff to say
> > > about using NTFS Compression.  I was in a meeting on
> > > Thursday, and MS Consulting was telling a customer this
> > > was OK.

> > > Imagine I create a clustered index on a table on this
> > > device.  Correct me if I am wrong, but isn't a clustered
> > > index about the physical organization of data pages on the
> > > disk, for fast sequential reads?  Wouldn't using a disk
> > > defrag utility (of course shutting down SQL Server so the
> > > file is not in use) blow SQL Server's mind as data pages
> > > are moved underneath it?

> > > Thanks