try this link=>

http://www.sqlugcr.net/Portals/23/Sesión%209-LogShipping.pdf

and this also,

http://msdn2.microsoft.com/en-us/library/aa198224(SQL.80).aspx

hi,

In Object Explorer, connect to an instance of the SQL Server 2005 Database Engine, and then expand that instance.

Is "shrinkfile with no_truncate " a good option to resolve this issue.?

OK , Good

Check whether ghost cleanup process is going on the database..

Thnks all,

so i can conclude there is only one option of "SQL Server service Restart" as Shrinking of tempdb datafile will take lots of time...

also my question is =>  Is there any...

Thnks Sugesh..

but my tempdb log file is not used heavily it's only 600 MB(checked through sqlperf(logspace),but the tempdb data file grows more rapidly..

one procedure creates a temp table nut it...

Thnks a lot to all 4 this wealth of info.

Just one update.....

If we reindex any table the statistics is also get updated.

do the follow. to ensure this

step 1)dbcc show_statistics(tablename,indexname)

observe the "updated" field (date  and time)

step 2)reindex that table

now again execute...

Hope you are using these trace flags in the SQL server startup parameter

1204 and 3605

These  trace flags will show you the deadlock information in the errorlog..

hope this helps !

Thnks a lot.. Sugesh,Arun...

Thanks a Ton............ Lowell !

Try by executing the exe from which you have installed the SQL Server 2000,In that select upgrade/remove and in that select the client network utility.

But just keep in mind if you restart the SQL Server services the database will go in a recovery mode...

I will also recommend to note down the servername,collation settings(if any) of database,service pack info(along with the cumulative hotfix etc),output of sp_configure and bcp of tables.

Hope this will help