Gail fixed your code, but I'll explain a little:

A CTE is really nothing more than a temporary view. Because of that, it acts just like a view when you interact...

Probably the most straightforward way to prevent divide-by-zero errors is to use a CASE statement. SQL Server SHOULD bypass any divide-by-zero evaluations if you tell it not to attempt to...

I'm a developer so I'm a little biased, but I'm not sure that "right-sizing" memory is the best approach. Memory is a relatively cheap way to increase performance for a...

I'd probably change my approach up a little bit.

SELECT Eq.EquipID, IE.Amount as EquipAmount

FROM Equipment Eq

INNER JOIN InvoiceEquipment IE

ON Eq.EquipID = IE.EquipID

WHERE IE.Type = 'A'

AND NOT EXISTS (

SELECT 1

FROM InvoiceEquipment

ON IE.EquipID...

I'm guessing your error rows destination is preceded by an OLE_DB destination pointing to the table?

What I've done in this kind of case is to do a two-stage insert. The...

It looks like Scott almost had what you wanted. You're wanting all records where there is a duplicate, which can be restated as "All records where a duplicate exists." So,...

One of the big changes that was made in SQL Server 2014 was that the cardinality estimator was significantly changed. This resulted in behavior changes, both good and bad.

Tom LaRock...

You can avoid the whole question of NULLs with NOT EXISTS. Also helps you to not abuse a LEFT JOIN.

ms-techie (3/4/2014)

---

Actually from CTE is like this .. All 3 are from SAME TABLE , with different conditions in each case

With CTE1 AS

(

Select count(Column1) as Cnt_Column1_Tbl1 FROM TABLE1 with some...

You could do it either with inner joins or EXISTS clauses.

As this smells a bit like homework, implementation is left up to the reader.

You have a lot going on here, but I'll give this a try anyhow.

My first observation is that I'd probably make your subqueries into CTEs, if just for separation of...

I'd schedule a job that waits several seconds, then creates the new job you want using the T-SQL script for the job.

There are a couple of dynamics at work here:

A) Table order is never guaranteed unless you use an order by or some ordering/filtering mechanism like ROW_NUMBER() or such. So, the...

The size is irrelevant. A...

Have you watched the I/O of the server while the queries are running? I know that, for example, we're limited to 600Mb/s for or developers, but the backups user can...