You can force the parameters to have default values or you can hide some of them or you can adjust the number of rows and columns.  You could have 10...

Those are kind of my go-to's.

One thing that could be an interesting check would be how much data is being transmitted across that connection at the time the query is...

Execution plans would be my starting point.  make sure that the queries are all doing the same thing.

Also make sure all queries are getting the same results.

Then I'd check wait...

I could be mistaken, but I am 99% sure that the problem is that a QUEUE is not the same thing as a TABLE.

I just checked that queue on my...

I am not sure what the question is.  Are you wondering if I think SQL Server will work better or if SQL Server will need the same indexes as MySQL...

As a thought - if you can translate the symbols to numeric values, you could do it with some messy WHERE clause.  What I mean is something like:

            
October 27, 2020 at 10:09 pm
            
#3801900

            
            
                                                
        

I imagine this depends on your CMS.

But it sounds like a use case for SSIS to me.  With SSIS you can have it fire queries against multiple databases simultaneously or...

My opinion - you get what you pay for.

The authors of the books need to make money, so they write books on what they know.

If free training is what you...

Found this article:

https://dba.stackexchange.com/questions/114572/why-does-updlock-cause-selects-to-hang-lock

From that link, the solution is to have a better index. Now, that being said, I would expect that since you are doing a SEEK, your index is...

Sounds to me like windows permissions are set wrong.  You said you can't access it from Windows run menu OR from SQL Server, this makes sense.  If you have no...

Have you tried using CAST or CONVERT to pick a data type on the column that has an unknown datatype?  Not the best solution, but will solve the problem.

What I...

Gotta love it when SQL can't guess how long the rollback will take so it tells you 0% and 0 seconds.  I've seen that before and there is that panic...

Sorry I couldn't be more help, but I am stumped on this one.

I am confident that restarting the SQL Server service will fix the issue, but I am confused why...

Well, I'm confused... the query I gave should have shown you the rollback status on the query.  Since sysprocesses and sp_who2 are both saying it is rolling back, my next...

Since the query didn't return anything, my thought is the rollback completed successfully. Where are you seeing the "killed/rollback" information?