Hi Bob,

>...running the upsizing wizard directly on that machine. Running it from the workstation took 5 hours to upsize 10% of the table. Running the upsize wizard directly on the SQL Server only took about 5 minutes.

I could easily blame this on the upsizing wizard code. You'd have been better off trying to BCP or DTS the data to SQL or to let the wizard create the structures and remote views, then populate the remote views with the data after changing the BatchUpdateCount.

>I then ran a few queries. Using SQL Passthrough, I can retrieve a single record with a simple query in under a second. This same query takes over 10 seconds on the workstation.

I'm not sure what you mean here. Did you do SPT on the server? What was different about the one-second vs the 10 second query?

>I then created a remote view on a single table using a single where condition. This query takes less than a second when run from the SQL server, yet takes over 10 seconds on the workstation.

This obviously points to extra overhead somewhere between your workstation and the server. There are ways to find out what's going over the wire, such as using the SQL Profiler or perhaps using the ODBC trace.

>Anyone have any idea why SQL commands execute so slowly from the workstation? It is not due to problems with hardware, etc.

I wouldn't discount hardware issues. It could also be a bad network connection, such as a bad NIC or wire. These things can be detected by a good network engineer.