Do take a database backup of after changing the recovery model

Try This One =>

create table #test(servicename varchar(50),status varchar(50))

insert into #test(status) exec master..xp_servicecontrol 'QUERYSTATE','Sqlserveragent'

update #test set servicename='Sqlserveragent'

select * from #test

You can also add trace flag 1205 along with the 1204 trace flag which will more details about the deadlock..

Check whether you have applied latest SQL Server service pack(SP2 refresh version) on the server

Cheers ! 😉

Dont Forget to take cold as well as hot backup before moving system databases. 🙂

I do agree that if virus scanning is going on those database files,it may give you a problem..

Thnks a ton Lester..it helped me also 😀

Please follow these steps :-

1) On your local machine,create linked server for each server you want to monitor.

2) Create stored procedures/write select statements on your local machine.

(You can use four...

Try this one...Hope it helps 🙂

select * from openquery(linkedservername,'sp_help')

kindly let me know the SQL Server version 🙂

Waw !!!

This helped me a lot.............:w00t:

Thnks a Lottt.............

u r gr8....:)

this might help !

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx

This is also a good link  =>

http://support.microsoft.com/kb/224071 

Thnks !

I think by exporting this registry value and importing this value to another client machine may help !

thnks a lot

this might help.....

in profiler Filter tab mention "Objectid Equals" to object id of that table.

you can find the object id of any table  like this..

select object_id('databasename..tablename')

specify this object id in...