Hi,

can you just try like this:

setup.exe /ACTION=UNINSTALL /FEATURES=Tools

Hi Chris,

Good topic & idea. Chris, I tried to create the trigger which is shown in the article. but i am getting syntax error. could you please...

once again thank much Mayank..this is what I was looking for.!!!:-)

Also thanks much for the link...

thanks Mayank...apart this one (sp_spaceused)..is there any DMVs to use to retrive index space info...

thanks guys..lets say i have a system having sql server 2005 sp2. last february there was latest security patch for sql server 2005. we have service pack 3...

Thanks Jeff...it seems the picture is much clearer now...thanks again

Thanks Steve..thanks much...

hi,

it is becuase in case if we have to change back to 80. lets say if we have any user objects in the master db.

thanks Steve... could you tell me the reason for cannot changing back to 80.

From the performance side, as far as I know shrink will cause page split and thus causing fragmentation on indexes.. if you really dont want to shrink it then...

I think we can get how many inserted/deleted/updates together from the column 'rowmodctr' of sys.sysindexes tables..

you can refer this link:-

http://www.sqlservercentral.com/articles/Transaction+Log/65877/

if you guys dont take Transaction log backups, you can change recovery mode of database to simple so that the transactions will be deleted in timelt manner...

make sure you guys...

sorry i think there is small correction:-

index defrag or rebuild comes into picture when:-

avg_fragment_size_in_pages =1000

avg_fragment_size_in_pages should be less than or equal ro 8, right?

please advise