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...

It's not one I've run into, but doing a few internet searches, it looks like 8695 is related to malformed XML for the execution plan. So, the question is then,...

You'll get a lot better response posting that question to the main forums. The only people who will see are those who responded to this six year old thread.

You simply have to supply the schema name when referencing the object:

myschema.TheTable
yourschema.TheTable

Instead of just reference the table name alone.

Test it all as best you can. No, I wouldn't plan on undoing the install. Plus, backing up master won't cut it. You're changing the underlying executables, so restoring an...

Sadly, there isn't a magic formula that nails this. Some individual statistics may need to be updated multiple times a day. Others may never need to be updated manually. It...

Oh, don't do NOLOCK. Yeah, it will enhance performance because it changes how locking and blocking occurs within SQL Server. However, especially if you're getting lots of large scans, as...

Moving the target of your build process to Windows could help solve issues. You could then install whatever tools you needed to that Windows instance. Control could still be through...