StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POSQL Server: Having clause with variables
primarykey
Id
5120256
data
AcceptedAnswerId
5120370
AnswerCount
4
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-02-25T17:05:31.037
FavoriteCount
0
LastActivityDate
2011-02-26T11:10:34.660
LastEditDate
2011-02-25T17:56:14.083
LastEditorUserId
13302
OwnerUserId
277136
ParentId
0
PostTypeId
1
Score
0
ViewCount
2744
LastEditorDisplayName
text
Body
I'm working on a stored procedure for an academic institution that would allow advisors to filter their student lists by a number of criteria. Recently, the advisors asked me to give them the option of filtering students by GPA. This was perfectly easy until they asked for an option to determine the inequality. Here's a truncated copy of the query I'm using, and the corresponding error message in SQL. <pre><code>DECLARE @Inequality CHAR(2) SET @Inequality = '>=' DECLARE @Gpa DECIMAL(3,1) SET @Gpa = 2.0 SELECT DISTINCT mem.StudentID, SUM(GradePointValue * Credits) / SUM(Credits) AS GPA FROM <snip> WHERE <snip> GROUP BY mem.StudentID HAVING CASE @Inequality WHEN '>=' THEN SUM(GradePointValue * Credits) / SUM(Credits) >= @Gpa WHEN '>' THEN SUM(GradePointValue * Credits) / SUM(Credits) > @Gpa WHEN '<' THEN SUM(GradePointValue * Credits) / SUM(Credits) < @Gpa WHEN '<=' THEN SUM(GradePointValue * Credits) / SUM(Credits) <= @Gpa END ORDER BY GPA desc </code></pre> When I try to execute this query, SSMS gives me the following error message: <code>Incorrect syntax near '>'.</code>, referencing the first line of the <code>CASE</code> statement in the <code>HAVING</code> clause, <code>>= @GPA</code> I've tried rewriting the <code>HAVING</code> clause to: <pre><code>HAVING SUM(GradePointValue * Credits) / SUM(Credits) CASE @Inequality WHEN '>=' THEN >= ... END @Gpa </code></pre> This produces another error message: <code>Incorrect syntax near the keyword 'CASE'.</code> I know I could copy and paste the entire SQL query four times and change only the inequality in the <code>HAVING</code> clause in each query, but that's messy (not that this isn't -- it just doesn't smell as bad to me) and I'd like to avoid it if I can. Is there any way for me to pull off my attempt above?
Tags
<sql-server><sql-server-2005>
Title
SQL Server: Having clause with variables
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USmarc_s
UserOwnerUserId
1. USjwiscarson
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.