Let's assume that the databases & queries are tuned (that's always a question for me though, tuning is an ongoing process, not a one & done proposition). For example, since...

Connection console? I'm not sure what that is. However, let's talk through using the tools to connect to a server.

When you open SQL Server Management Studio, you should see this:

One aspect of remote queries you can't affect is the data being moved between the two systems. If you move one million rows (just plucking a number out of the...

It's really hard to tune a query that returns everything. In fact, you can't. All you can do is throw hardware at the problem. Buy more and faster CPUs, memory,...

No need to drop the table. It'll get cleaned up by internal processes once that procedure completes.

Now, we could talk about using a cursor to insert rows into a table....

Sounds like either bad parameter sniffing or out of date statistics or a combination of the two.

The way that the query optimizer works is it uses the statistics to come up with row counts (estimated or actual). Based on those counts, it makes decisions on how...

I'm going to be as honest as possible. I don't remember how 2005 works any more.

However, yes, you absolutely can upgrade SQL Server to 64bit on 2005. Doing so changes...

I've worked for smaller companies where, as the DBA, I was responsible for everything. From installing the physical server, to patching the OS and SQL Server. I've also worked for...

Capture the execution plans between the two users, the one that's good and the one that's not. Compare them (you can use the SSMS tool to do this). Look specifically...

Also, is 2 ms worth optimizing further?  Even if you get a 50% increase in performance, that is going from 2 ms to 1 ms.  Having a spike in...

Another way is to use Extended Events to capture wait metrics for the query. Alternatively, use sys.dm_os_wait_stats (for on-premises, sys.dm_db_wait_stats for Azure SQL Database) to capture the wait statistics....

Whoa!

You are literally begging for a SQL Injection attack with this code. I'd strongly suggest you read up on what that is and how to prevent it.

Next, you're trying...

Wouldn't you just add o.status to the SELECT list? I'm confused by what the question is.

SQL Server, by default after an install, will attempt to use every bit of CPU and RAM that the system will let it have. Assuming you've changed none of the...