Yes, it can be done using MAX() and probably a ROW_NUMBER() to prevent aggregation.

If you post the sample data, I can show you how to do it.

It's not needed.

It's probably a misconception coming...

Yes and no.

I declare the variable like that but it could be any date to get historic reports. I believe that I tested it with a simple GETDATE().

I got confused with your explanation. Could you post DDL and sample data (as insert statements) along with expected results based on that sample data?

That will give you better and...

Brandie Tarvin (1/15/2015)

---

Sean Lange (1/15/2015)

---

I am having a discussion with somebody who swears that using

EXISTS(select 1

is way faster than just select *. I know Gail has an article on...

Have you checked the Synonyms?

You need to split the data in your Value column. If possible, normalize the table so you don't have to work like that.

To split the data, you could use the...

Edna Mode

---

No...

Use the variabale in the WHERE clause.

select *

from @t

where IsSalaryApproved = @IsSalaryApproved

EDIT: Sorry, I need more coffee to read carefully.

Congratulations Koen! When I grow up I want to be like you. :hehe:

I would suggest you to follow Sean's advice. You have a simple front end available called Reporting Services (SSRS).

It's a powerful tool that you could use to prevent this kind...

Even if it's readable, I wouldn't suggest using Stephanie's code. It reads the table 7 times which can become a nightmare on large tables.

Hi, here's one possibility to get that report. There are other possibilities but this just seemed easy for me.

SELECT CustomerID,

DATEDIFF( MM,

...

So the problem was when calling the stored procedure.

If you corrected your app code, you shouldn't have changed your stored procedure.

Without more information, I have 2 possible guesses:

Your column transaction_date_time is a string that you're comparing to a datetime and that's causing the error. To correct this error, you...