Posted by Erland Sommarskog on 04/14/06 00:22

pb648174 (google@webpaul.net) writes:
> So there isn't some source out there that has the script posted on the
> net? If this is something that should be done for every single
> database, why should every person write their own and go through a
> development bug fix cycle to figure out what they are doing wrong? I'm
> worried about throwing something together and it causing more problems
> than it solves (right now we have no problems as far as I know related
> to indexes or fragmentation for databases in use for years).

I didn't say that there is not anything publicly available for this, but
I was too lazy to start searching for something. As a matter of fact the
code that we use to get the tables with 30% more fragmentation was some-
thing that SQL Server MVP Andrew Kelly posted to
microsoft.public.sqlserver.tools once. (I believe that it was that news-
group, but I could be wrong.)

SQL Server comes with maintenance plans where you can set this up,
and probably get some default. But the problem is, that this is not a
case of one size fits all. There are several factors involved: how
much data is inserted? updated? deleted? What availability requirements
do you have? Do you need to use GUIDs etc.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]