Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 441
  • Last Modified:

valid SQL statement?

Is this SQL statement valid?  refering to the "and"

Group BY item.inv_units_Pack and user_comp_permission.id_user = 37
0
tesla764
Asked:
tesla764
6 Solutions
 
ravikantninaveCommented:
use
Group BY item.inv_units_Pack HAVIN user_comp_permission.id_user = 37
0
 
r3nderCommented:
no
Group BY item.inv_units_Pack,user_comp_permission.id_user = 37
0
 
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
<guess you mean this>

SELECT item.inv_units_Pack, -- one or more aggregated column such as SUM(), COUNT()
FROM -- some table(s)
WHERE user_comp_permission.id_user = 37
GROUP BY item.inv_units_Pack
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
r3nderCommented:
or like this
SELECT top 10 TelemetryUID from Telemetry Group by TelemetryTime, TelemetryUID,BitTripNumber  HAVIng BitTripNumber = 2
0
 
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
Couple of things, somewhat redundant with above columns...
*  Columns in GROUP BY are separated by commas
*  You can't have an logic expression in a GROUP BY

btw if it helps I have an article out there on SQL Server GROUP BY Solutions that would be a good read.   If it helped you please hit the 'Yes' button at the end.
0
 
PatHartmanCommented:
Having and Where are applied in different stages of the query and so can have different effects.  They can both be used in the same query but if you build the query with the QBE, you need to be careful to specify WHERE when that is what you want since totals queries will always default to using Having.

WHERE is applied BEFORE the data is aggregated so you would use the Where clause if you were not including the field in the selection clause.  So the query selects all data prior to today but doesn't include the date in the aggregation.
Select fld1, fld2, Sum(fld3) as SumOfFld3
From yourtaable
Where fld4 < Date()
Group By fld1, fld2;

HAVING is applied AFTER the data is aggregated so it is most often used on some aggregate value.  Same as the first example except that after the data is aggregated, you apply a Having to select only rows where the sum of fld3 is greater than 333.
Select fld1, fld2, Sum(fld3) as SumOfFld3
From yourtaable
Where fld4 < Date()
Group By fld1, fld2
Having Sum(fld3) > 333;
0
 
tesla764Author Commented:
Thank you for your respones everyone. This is not my code and I deal with many languages.
I think you are telling me that the "and" being used is not correct?
0
 
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
Well, the error message that would be returned when you execute it would tell you that it is not correct.

All of us are guessing what you're trying to pull off, and the correct way of doing it.  So if that's your intent, please provide us some more details as to what you're trying to do.  Preferably with a data mockup of what your data looks like now, and what you're trying to accomplish.
0
 
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
Thanks for the split.  Good luck with your inherited code.  -Jim
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now