yes, you are right, but I was using that as part of the sql processing, so I was hoping that someone might know.

Can you send me few links, if any, on how to output the execution of stored proc to the text file?

Actually thanks for reply, Jeff. As your reply helped me found a bug.

I need to revisit my code again.

Thank you

Gurus,

Thank you very much for your help.

Is there a way you can explain the interaction of

WITH T(N) AS (SELECT N FROM (...

Thank you,

Number increments from 1110 till 1150 and then it starts again from 1210 till 1250, etc....

Once it reaches 1550 (2550/3550.../8550) it jumps to next thousand:

1550 -->2110

2550-->3110

3550-->4110

.....

8550-->9110

*****************

1110

1120

1130

1140

1150

1210

1220

1230

1240

1250

1310

1320

1330

1340

1350

1410

1420

1430

1440

1450

1510

1520

1530

1540

1550

2110

2120

2130

2140

2150

2210

2220

2230

2240

2250

2310

2320

2330

2340

2350

2410

2420

2430

2440

2450

2510

2520

2530

2540

2550

3110

3120

3130

3140

3150

..................

9510

9520

9530

9540

9550

Thanks Guys for your input,

Igor,

can you please elaborate on ...if you do REORGANIZE on big indexes and then update their stats, then you'd better check the time for only REBUILD...

Thanks Jeff,

I have over 20 steps in the Sunday Maint Plan.

Among them:

Backup before Maint, put DB in Simple Recovery, Disable auto update statistics, dbcc checkdb, Reindex, Update Staisticsts, put...

Anyone else?

Gurus, Any more suggestions?

Thanks for your reply.

I am running reindex (reorg and rebuild) in parallel threads (in multiple jobs) simultaneously, so I cannot run sp_updatestats before reindex step

Thank you,

Yes - I am planning to select indexes which were "REORGANIZE"d (no statistics update) during reindex maintenance along with other indexes, where statistics were not updated for the last...

Hello again,

As my Production database approaching 400GB, issue with sp_updatestats using the default sampling rate (which potentially can skew the performance) bothers me.

Running below takes way too long:

USE dbname;

EXEC sys.sp_MSforeachtable...

Part of out main application has been build by 3rd-party vendor and only recently (less then a year ago) they became SS2K8 certified.

Thanks for your help.