I like how xkcd explained it, http://xkcd.com/1425/

No.

In general it raises some potentially bad issues.

1. General users will likely not know how to write proper queries, this can lead to 2 things, first performance hits and second...

Geezer

mariandalalau (8/24/2015)

---

If I put max([DateCreated]) in the select the result is the same, actually the DateCreated is the same for all records in the same group. The problem is that...

/shrug it's a compliance issues, it's not supposed to be useful and the vast majority of it can be summarized as use common sense.

We have to go through a bunch...

Eric M Russell (8/20/2015)

---

Jeff Moden (8/20/2015)

---

Iwas Bornready (8/20/2015)

---

I just worry about the programmers that want to "fix" something that isn't broken, just to make it more efficient. As often as...

Hmm.. depending on the query 8GB memory for a 100GB DB could be an issue. Improving the query might help some but if possible can you just work with...

Mistakes happen anytime you're developing something new that's just part of development, and the more radical the new development is the more likely you'll find odd and potentially critical issues....

ah...

What about something like?

SELECT week_id, jobnbr, tasknbr FROM @data WHERE item_type = 'TASK' OR (item_type = 'HOLD' AND item_id != 'MATL')

GROUP BY week_id, jobnbr, tasknbr

HAVING SUM(CASE WHEN item_id = 'MATL'...

Fire

Are you sure this is a SQL Server issue and not an issue with the application?

ssk7317 (8/7/2015)

---

I understand that genrally making them use one ID is a disaster. But we are doing it along with tool called Cyberark which is the conduit for DBAs to...

There really is no one size fits all solution to data analysis or reporting. Data analysis is supposed to answer question and reporting is supposed to deliver those in...

Hmm... what's fun is when good processes get built around bad processes and then the bad processes can't be fixed without redoing a lot more things.