Robert, i had a similar problem once, Take a drastic measure, disable all the jobs and enable them one by one, see which job causes your SQL to freeze, then...

I would have a very good disaster recover plan in place, check for index defragmentation on a regular basics 🙂

AS said Verify option verifies the file, for your peace of mind and as best practice, you can restore the databases on a test server on regular intervals ...

Try SSIS 😀

First thing that comes to my mind is the improved database engine 😀

thanks mate, This looks great, i am a bit concerned about the security, since they going to be on my production server, i can understand, still it will be good...

i tried mate, it says could not find store procedure, i am using SQL 2005 64 bit, does this make any difference 🙂

I will check the forum as well, please...

If you have a testing server, try in that first and so you will know the importance of the points mentioned above, then there are lots to look once migrated...

Hi Zoma

What run time error is it throwing out, can you post the error 🙂

Try without AT @Linked_Server, it will work, its working for me, what version of SQL are u using mate???

instant solution, if you can try to restart SQL server, and then find the cause of it. 🙂

The easy way is to check on Syslogins, from there you can see the createdate, updatedate and accessdate of all logins for the server. you can play around with this...

Check the process that access the SQL and check the codes, if its a SP then try to improve performance by findnig bottleneck, as suggested i would use profiler to...

Thanks Mascott, u definetly cant kill or do anything on system process 🙂

Thanks mate

I can see that, but i am just worried about the system performance, will this affect any performance???? ...