SQL_ME_RICH (5/22/2013)

---

Hey Mister Magoo!

Well - that definitely changed things, but now it creates a whole new error all together (I went back to the first set of INSERT statements, and...

Try this

DECLARE @ReportDate DATE;

SET @ReportDate='8 jan 2013';

WITH data AS

(

SELECT * ,ROW_NUMBER() OVER(PARTITION BY ConsumerID ORDER BY ActivityDate DESC) AS rn

FROM dbo.ConsumerActivity

WHERE ActivityDate <= @ReportDate

), cons AS

(

SELECT ConsumerId, MAX(CASE WHEN rn=1...

Instead of replacing 'NULL' with '', try replacing 'NULL' with NULL

marc.snoeys (5/17/2013)

---

That's basically my point 🙂

There is nothing wrong with the INSERT-statement at all.

But, my personal opinion is that it would be more intuitive to be able to write an...

Unfortunately, unless you mangled that XML while posting, you will have to use string processing on that as it is not valid XML.

Got to say, just add a Manufacturer column and do away with the LIKE query...

that's an understatement...:-P

mayabee: Cursors and procedural code inside triggers are a really bad idea, consider writing the IDs to another table and have a separate...

sqlguy-736318 (5/15/2013)

---

yes - the code folding in that screenshot appears to do more harm than good.

However, you mentioned a plugin could be written to use regions in a way that's...

Craig's idea sounds great!

Before I saw it, I came up with this , which is similar but different to Wayne's method for tying the rows together...

Just including it as an...

This is a very simple problem to solve.

Look at character 79 of that statement (as it tells you in the error message) and you will see this character : “

It...

I can't see why this is in the results?

select 79673, 49202

Can you explain?

Both.

It is single level and automatic, so you can't define...

sqlguy-736318 (5/10/2013)

---

I downloaded SSMS Tools Pack and the region functionality seems to be a bit quirky. For example, for 2 regions on top of each other, collapsing the top...

GilaMonster (5/8/2013)

---

As for splitting the logic out, excellent idea if there's only one parameter, borderline if there are 2, near impossible over that. For 5 parameters you're looking at needing...

Can I wave the flag for separating out the logic completely, either in two distinct stored procedures (one for queries with the optional parameter, one without) or by use of...