You can use the following sample script to do it but your table will be offline during this operation. If it is large table it will take good amount of...

You have to use the permon counters based on your requirements.

Here is the link for basic counters.. http://www.sqlservercentral.com/columnists/sjones/performancemonitoringbasiccounters.asp

http://www.sql-server-performance.com/sg_sql_server_performance_article.asp

http://www.microsoft.com/technet/community/chats/trans/sql/sql0513.mspx

http://www.sql-server-performance.com/sg_sql_server_performance_article.asp

May be your load process holding the locks on the table.

run your script with

If you want to defrag hard disk not the sql server table you can use disk deframenter comes with windows. If your dbs are attached to SAN check your SAN...

http://groups.google.com/group/microsoft.public.sqlserver.programming/browse_thread/thread/2f35e411e73b0306/af21f3245b7227d2?lnk=st&q=sql+server+2000+bCP+directory+service+layer%3A+internal+directory+control+layer+error%3A&rnum=2&hl=en#af21f3245b7227d2

Negative.

No it is not removed. What edition are you using? If you are using SQL Express, I think it is not there...

In other editions...

SQL management studion/Management/MaintenancePlans

http://msdn2.microsoft.com/en-US/library/ms189036.aspx

Anything in application/system log?

Did you install SSL or enable encription?

At this time you will get table script also along with indexes in SSMS.

If you want to only index script you have to write your code using DMO..

http://www.karaszi.com/SQLServer/info_generate_script.asp

http://blogs.msdn.com/dtjones/archive/2006/08/23/714738.aspx

 http://www.sql-server-performance.com/faq/sqlviewfaq.aspx?faqid=144

You can't restore or attach system databases from 2000 to 2005.

You can script all the jobs and run that script on 2005.

There is no guarntee all jobs should run successfully....

For small db it should be fine where as for large dbs it will be pain and take long time

Backup restore is the best and simple way move the data...

Backup restore should be fine if the larger dbs...if the dbs are smaller I will go with detach/attach...

log reader, snapshot, distribution and merge agents should be suspended before final tlog...

Upgrade sequence should be Distributor, publisher and subscriber...

Upgrade first distributor and publisher...if you don't have time you can upgrade subscriber later for one way trans. replication but it is advisable...

If the db is 100 mb then backup the database and zip the file and restore it

OR

You can do snapshot replication too over internet...