It's kind of a broad question but ultimately depends on what constitutes "business logic". I generally fall on the side that says databases should be stupid and do what they're...

Maybe I'm dense. I see how you resolved your reference problem but I don't see how you solved your dependency issue which is why those references are important. For example,...

Any individual row might get updated, on average, a couple to three times in its lifetime so it's probably not that big a concern; however, I'll keep an eye on...

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 ( TimecardIndex, EmployeeID...

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

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

Grant Fritchey (12/1/2014)

---

Robert Frasca (12/1/2014)

---

Grant Fritchey (12/1/2014)

---

The pain point on the WithMAX plan is the fact that it's doing a Loops join against 1.9 million rows. That's effectively a cursor....

Grant Fritchey (12/1/2014)

---

The pain point on the WithMAX plan is the fact that it's doing a Loops join against 1.9 million rows. That's effectively a cursor. But, it looks like...

That's weird. I'll try attaching them again. I did the attach and upload. I'm not sure whether there's another step.

Putting SSIS on it's own box has many benefits, mostly by distributing load, in fact it was designed to be used this way. Hopefully though you use dataflows and not...

Figured it out I think. I was right-clicking the view name and clicking SELECT TOP 1000 ROWS so it opens a new query window and runs it in the context...

If I remove all the filters the SQL:BatchCompleted event is captured for the database for which I was originally filtering.

When I add the database name filter back in it is...

I have one filter to include my specific database name, i.e. LIKE 'DatabaseName' and I'm running this against a dev machine remotely. (I'll look at extended events as I haven't...

Well, now that you mention it, the source database is SQL Server 2005 while the target is SQL Server 2012. In my test environment, both db's are in SQL Server...

The bottom line is that I can only get it to work on this particular machine if I embed the query in a stored procedure that I must store in...