If the linkedservers were setup to use remote login then you can drop and recreate them. You can execute sp_helplinkedsrvlogin to find out remote logins.

Make sure the user logout and login, or reboot, to gain the new credential.

It seems the SQL login has the proper permission to server1.db1.owner.table. Make sure the Windows login has the same permission as SQL login.

Thank you all for your valuable insight, I really appreciate it.

Jimmy

Thanks to both of you. Are there anyone else would like to share your experience ?

Thanks...Jimmy

I found the following VB code on the web that does what I need:

Option Explicit

'========================================================

' API Functions

'========================================================

Private Declare Function GetVersionEx Lib "kernel32" Alias "GetVersionExA" & _

    (lpVersionInformation As OSVERSIONINFO) As...

Thanks for the reply. What I'm looking for is the client's OS, not the server's OS.

exec msdb..sp_start_job @job_name='job_name', @server_name='server_name'

If you plan to install SQL Server 2000 SP4, don't forget to install the hotfix that addresses the AWE issue. See KB article 899761.

I found out that you can download the Bulk Export Task from:

http://www.sqldts.com/default.aspx?272

Take a look at KB article 314530

Are you sure the sp is not running ? are you using sp_who2 to check for process blocking itself ?

FYI, SP4 now checks blocking spid for latch wait in...

We don't use AWE. So that's not a problem for me. My concern is that I have seen users who have installed SP4 and are experiencing query performance issues. Is that...

Have you run CHECKDB ? If not, run it at non-business hours.

Thanks for taking the time to reply. I really appreciate it.

In my case, I'm just creating a local partitioned view. Do I still need to turn on XACT_ABORT SET ?

Thanks...Jimmy