I told the user to reboot the VDI  and after rebooting multiple times the issue still persist but when the user takes RDP to the server it works. Not able...

We did few query tuning and it seems the user are good so far.  Thanks for your support on this. It helped me a lot.

Thanks for the details.

I too guessed it should be buffer pool size which cause this issue but they don't get this error when they run after some time.

I will try...

1 - are you fully patched?

yes we are fully patched

2 - is the latest .NET installed?

yes it is

3 - how are you calling the linked server?  Is it a 4-part...

It has both reorg and rebuild. My index job runs through a different tool so it keeps to retry even if there is a interruption in SQL connection

Thanks for the response.. it worked as you mentioned.

Yes i did and one more thing do i need to restart SQL server post SPN registration.

I can find the file open it and work but the problem is when i type SSMS in start- > run it doesn't take me to management studio

This script works good, but in my environment I have 100 dbs so I need to take first 50
DB in one path and second set in...

I had given db owner , targetserverrole access to MSDB database so he is able to view the jobs when he tries to connect from enterprise manager(sql 2000 instance)...

in output file it is mentioned like we don't have sufficient permissions to start the agent

i think if you upgrade to SP2 you will be out of this error..there is no proper ans when i googled out this

We can't bring a DB from restoring mode to offline mode but we can bring it if it is in a stand by mode. so i will try it in...

Hi chandra mohan

your options will work for a DB which is online mode but not for a DB which is in restoring mode. So let me know how to change...