ChrisM@Work (8/7/2014)

---

ScottPletcher (8/7/2014)

---

ChrisM@Work (8/7/2014)

---

Each reply posted to your question implies "maybe", "probably" or "definitely". The average of these...

ChrisM@Work (8/7/2014)

---

Each reply posted to your question implies "maybe", "probably" or "definitely". The average of these isn't "definitely...

They definitely could. The WHERE conditions determine...

Bill Talada (8/6/2014)

---

To be chosen as a deadlock victim, two threads must be inside transactions. If thread one updates tableA then tableB while thread two updates tableB then tableA...

For best performance overall, I strongly suspect you need to change the clustered indexes on the tables. We would have to look at least at missing index and index...

LutzM (8/6/2014)

---

Here are a few options to make that single table "smaller":

If the table contains a rather large number of columns (e.g. 50 or more) you might consider "vertical partitioning",...

Again, I urge you to...

For that, you could create a proc on the remote server. You execute the proc remotely, and the proc can issue the start job, and then monitor for job...

8 hours seems extraordinarily extreme for 172M rows. It seems like there must be more to the story.

Are you changing the clustered index on the table? Does the...

I'd also create the best indexes while re-working the code.

#Events indexes:

1) Unique Clustered on ( ProcessDate, L4Ident ) --in that order

2) Nonclustered on ( L4Ident )

3) NNonclustered on ( LinkRL4,...

dkriplani97 (8/1/2014)

---

this update statement is working

UPDATE TableA

SET Value = isnull((select top 1 Value from #tmpcopylibrary

where dataid = tempquerydataid), 0).

however this is not working

UPDATE TableA

SET Value = isnull((select top 1...

OPENQUERY does not allow variables, only literal/static queries.

Try code below instead.

--temporarily add "TOP (100)" to the query for testing purposes

SET @tsql = STUFF(@tsql, CHARINDEX('SELECT', @tsql) + 6, 0, ' TOP...

Eirikur Eiriksson (8/1/2014)

---

ScottPletcher (8/1/2014)

---

If the table may or may not exist, you'll have to make references to that table only in dynamic SQL. Otherwise, if the code runs and...

If the table may or may not exist, you'll have to make references to that table only in dynamic SQL. Otherwise, if the code runs and the table does...

Agreed, nice code.

But if it's a birthday, wouldn't it be reasonable to use the current date + 1 as the cutoff, since there won't be future birthdates but someone could...