Robert Frasca (12/2/2014)

---

Grant Fritchey (12/2/2014)

---

ScottPletcher (12/2/2014)

---

Robert Frasca (12/2/2014)

---

ScottPletcher (12/2/2014)

---

Robert Frasca (12/2/2014)

---

ScottPletcher (12/1/2014)

---

I guess the SourceFactTimeCard table is fairly wide?

I suggest creating a covering index on:

SourceFactTimeCard (...

Robert Frasca (12/2/2014)

---

ScottPletcher (12/2/2014)

---

Robert Frasca (12/2/2014)

---

ScottPletcher (12/1/2014)

---

I guess the SourceFactTimeCard table is fairly wide?

I suggest creating a covering index on:

SourceFactTimeCard ( TimecardIndex, EmployeeID )

If SQL then...

eric.notheisen (12/2/2014)

---

In our company sharing user passwords is a firing offense. As developers needing to troubleshoot user defined defects, we restore the production database to our development VM's and...

Robert Frasca (12/2/2014)

---

ScottPletcher (12/1/2014)

---

I guess the SourceFactTimeCard table is fairly wide?

I suggest creating a covering index on:

SourceFactTimeCard ( TimecardIndex, EmployeeID )

If SQL then uses that covering...

SQL allows you to designate a proc(s) as "start up" procs that automatically runs when an instance starts. I was suggesting you create such a proc, or add code...

I guess the SourceFactTimeCard table is fairly wide?

I suggest creating a covering index on:

SourceFactTimeCard ( TimecardIndex, EmployeeID )

If SQL then uses that covering index -- it...

SELECT CONVERT(varchar(10), DATEADD(DAY, DATEDIFF(DAY, 0, dt), 0), 120) AS dt, SUM(amt) AS Amt

FROM @t

GROUP BY DATEADD(DAY, DATEDIFF(DAY, 0, dt), 0)

You can pass @StartingDate as a param to the ITV function.

Also, you can simplify the calc for PastPeriods:

MONTH(@StartingDate) % 3 + 14

You'll need to create a start up proc for each instance that checks for the different conditions.

Since you have to change both instance's memory settings, I'd create a proc in...

ZZartin (12/1/2014)

---

ScottPletcher (12/1/2014)

---

GilaMonster (11/30/2014)

---

I didn't say stop using select. I said stop using SELECT *. Explicitly define what columns you need and...

GilaMonster (11/30/2014)

---

I didn't say stop using select. I said stop using SELECT *. Explicitly define what columns you need and you won't...

Also, as additional stop-gap measures:

1) review indexes to see if there any you can drop

2) if you have any heaps, see if they consume a lot of space beyond what...

zedtec (11/25/2014)

---

I've also noticed when I go into my tempDB database properties through SSMS I get the following error:

ERROR 1222 : Lock request time out period exceeded.

I killed a session...

In theory, the code below would do what you've described.

select t2.*

from Table2 t2

where

exists(select 1 from table1 t1 where t2.detail like '%' + t1.ID +...

ZZartin (11/21/2014)

---

g.britton (11/21/2014)

---

good point, though...