Mohit ,the problem is that whoever runs a select * statement in that table creates lock.

First you connect to that particular database using login 'system'

ie conn system\password@DB_Name as sysdba. Then try

Check your database collation settings.

That depends on your query .Either you can create a composite key using two columns or a clustered index on that particular column.

If your queries mainly use that particular...

I know its in master database but in activity monitor its showing database_name.dbo.spt_fallback_db.

when giving NOLOCK hint there is no problem without that its worst.

The issue get solved when i reorganized...

The best way to shrink log file is to take a transaction log backup

then issue checkpoint and run the dbcc shrinkfile command

Hope you are not trying to remove the primary file.

Please post the error you got .

Hope the staging and production servers both are SQL Server 2005.

Use backup and restore if you want to keep database in staging server.

Does your database have lot of transaction?

If your database needs that much log then even if you shrink the log file it will come to that value which it want...

Select the exact file name by using

select * from sysfiles.

Please go through this

http://msdn.microsoft.com/en-us/library/aa260689(SQL.80).aspx

I tried that and found the version.But i just want to know is there any other way to find the version.

I tried using a Hex editor but I am not...

Can you please explain? I tried opening in notepad but i didnt find anything..

Change Remote Query Timeout to '0' in Server properties-->connections

Thanks for the reply Christopher,

The tables dont have any triggers. Is there any problem with the logic or order of execution in that query?