nadersam (3/8/2010)

---

Thanks for ur reply.

Yes i am doing this on production db.

i tried doing it first from mangment studio, it gave me time out so i generated sql script but...

certainly...that's y we plan our day to run maintenance activity..also a drop statement on large table with around 1000 transactions/sec is also not a good idea...

GilaMonster (3/8/2010)

---

Please don't automatically drop

You can drop an index at any time, neither the DB nor the server have to be in single user mode. If the index is...

as per me it will not cause clustered index to rebuild.

yes...if its a production server then u must wait for the maintenance window...other wise change the database to single user mode and drop the index..but before dropping the index u...

use TFS or subversion..don't use VSS....google for TFS tutorials...

plz mention sql server edition and service pack info.

post the script

appreciate your efforts..u should better try the dos script..it is fast and simple...

google "upgrading sql 2000 to sql 2005"

r u restoring primary file group??

am with George...

I was in a similar scenario...I found out the wait type of blocked process was cxpackets..

Use this query to filter out the blocked process and check...

connect thru ssms or sqlcmd to run the command

try this dos command, u can have it scheduled...

FORFILES /P <filepath> /S /M *.BAK /D -1 /C "cmd /c del @file"

try this...

select srv.name,lgn.Remote_name

from sys.servers srv, sys.linked_logins lgn

where srv.server_id=lgn.server_id

and lgn.remote_name='login1'

also refer to the BOL link

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/06d53a67-7804-4f1f-8201-3e42dc48ba79.htm