Sounds like a great place to put a wrapper proc. Have it have the same name and parameters as your current procedure. Then, inside it, it figures out which of...

Sean Lange (4/3/2015)

---

I found it a rather fitting response to somebody who clearly seemed they...

OK. Funny, very funny, but a little uncool.

Instead of killing all the processes directly, you could run your query, capture the ones you're going to kill, then simply set the database to restricted user and use rollback...

You're doing an INSERT and then want to use the values inserted later within the same query? How about using the OUTPUT clause to capture the values into either variables...

Try rewriting it to:

SELECT @KUR = RATES1 FROM dbo.L_DAILYEXCHANGES WHERE EDATE= @T1 AND CRTYPE =1;

But, it's only going to work if that only returns a single value. If it returns...

Rather than just killing the processes, understand what those processes are doing and why you're getting "massive" locks from them. And locking is a normal part of inserts, so it's...

That's good. What did it advise you to do?

For what...

I work for Red Gate

You can use Red Gate SQL Compare[/url] and SQL Data Compare[/url] to look at the backup and retrieve just a table and it's data.

I don't have specific scripts that I can supply you. However, the documentation is very clear. You can use the HyperV cmdlets to query the hypervisor. You can then use...

You have to use NEWID() to generate new values for a UNIQUEIDENTIFIER column. You might also want to look at NEWSEQUENTIALID() (in the same documentation).

Eirikur Eiriksson (4/1/2015)

---

Quick thought, this is NOT a tuning task, this demands a complete rewrite! Anything with the cardinality in excess of 10^12 going through both HASH MATCH 8 times,...

It's only 238 lines. That's what, two printed pages, maybe three. We don't start talking about how evil a query is until it breaks at least 10 printed pages.

So, we...

I don't know of any way to query the hypervisor from within T-SQL. Not directly. Assuming the login your SQL Server instance operates under has permission to the hypervisor, it's...

Still ought to see some sort of error. Maybe you're just getting a timeout while it waits for a lock to clear? What's calling the truncate statement?