we qa'd SQL 2005 SP1 and that is what we are installing until our QA signs off on SP2 and that is going to be months away. for now it's...

i would at the minimum have a RAID1 volume for the OS, another one for the mdf/ndf files and another for the ldf files.

we have a server where we dumped...

my strategy is i run the offline script first then the online script, repeat for each database. and then run the stats scripts.

i start with the biggest database and then...

i posted earlier versions here a few months ago and i spent time cleaning them up a bit. This whole system is at around version 0.8 and i still have...

and my update statistics script

USE [SCS]

GO

/****** Object: StoredProcedure [dbo].[usp_update_all_stats] Script Date: 04/09/2007 15:45:56 ******/

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

ALTER PROCEDURE [dbo].[usp_update_all_stats]

AS

/* Declare...

and my online script

USE [SCS]

GO

/****** Object: StoredProcedure [dbo].[usp_alter_index_online] Script Date: 04/09/2007 15:44:21 ******/

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

ALTER PROCEDURE [dbo].[usp_alter_index_online]

AS

/* Declare Variables */

DECLARE...

here is my offline script

USE [SCS]

GO

/****** Object: StoredProcedure [dbo].[usp_alter_index_offline] Script Date: 04/09/2007 15:43:17 ******/

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

ALTER PROCEDURE [dbo].[usp_alter_index_offline]

AS

/* Declare Variables...

next create a job that will gather all your index frag statistics. Create a step for each database. make sure to change the database id numbers for each db and...

next create a default. Make sure to change the server name to the local server name. I'll explain later.

USE [Index_Stats]

GO

/****** Object: Default [dbo].[server_name] Script Date: 04/09/2007...

First create a database on each server called index_stats.

Next create the following tables.

USE [Index_Stats]

GO

/****** Object: Table [dbo].[physical_stats] Script Date: 04/09/2007 15:35:17 ******/

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

SET...

I'm going to hog up a few posts with this, but here is the strategy i worked out. It's extremely flexible and in our case we went from 100% offline...

thx

don't know why we didn't think of it. might try it in the next few weeks as we are looking at scheduling an upgrade to sql 2005 for the publisher...

used to be MS service packs were like Star Trek. Evens are the best and the odds are the problems. looks like it changing

just got this today one one server

i'm running the system view with the detailed option for two other databases on this server and others and it works. i added another...

uninstalling and reinstalling IIS solved it

i think it was caused by SP2