I agree that there is a datatype issue as I am trying to do the same thing. I was stuck on a PostgreSQL BPCHAR datatype and got the same...

You might also consider Log Shipping the database to another server and scheduling the log restores to run nightly. Another option is to mirror the database to another server...

Sorry, I forgot to mention to check the properties of the linked server and make sure that Rpc and Rpc Out are set to True.

I'm just curious why you would be getting a MSDASQL error on an IBM driver. In our linked servers we connect with either ODBC (where the provider is IBM)...

I've seen that error on SQL 2000 when the server was out of memory (don't recall if it was SQL Server or a linked server). This was an older...

Our company hired contractors to create our Teradata data warehouse and also create all the ETLs from the SQL Servers. I don't know if you are familiar with Teradata,...

You can execute sp_who2 and look for the cluster user account under Login. The active node will be the Hostname column. You can create your own procedure to...

I just wanted to add a comment. When analysts are accustomed to Query Analyzer they may not be too thrilled to have a query tool that doesn't do as...

SQL may be caching the user account info. Can you drop an account, stop / restart SQL and then add it back again? If that doesn't work then...

I had something similar happen with a linked server on a 64-bit SQL 2005 connecting to a 32-bit SQL 2000 (error 10054: communication link failure). The NT account in...

Are your database backups on the server as well? Can you add an external array? I ran into the same situation a few years ago and we added...

I did a 2-step process: Upgraded a 32-bit SQL 2000 cluster to SQL 2005 (had the 64-bit cluster installed and ready in case there were problems), then later moved...

We mirror a 450 GB database and I see no ill effects. If the connecton is broken between the primary and secondary server, the log is still backed up...

Have you capped the SQL Server memory? If so, try different amounts--maybe 2816 or 3072. Did you stop / start SQL Server? (Don't remember if this setting...

Try registering the server with the IP address instead. Sometimes I see that error if a server name has been changed or if there is a problem with DNS....