StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
543261
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-02-12T21:07:41.677
FavoriteCount
0
LastActivityDate
2011-08-28T23:43:25.357
LastEditDate
2011-08-28T23:43:25.357
LastEditorUserId
149
OwnerUserId
149
ParentId
543101
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
The way you have your statement coded now will work (once you add the column reference to the case statement, as mentioned by other posts), however, to let the rest of your syntax go uncommented on would be a disservice to others in your situation. While you may only need to run this query once, I and others have run into similar situations where an <code>Update</code> to multiple rows also relies on data 3 or 4 tables away from our source and has to be run many times (like in a report). By collapsing your sub selects into a single <code>select</code> statement and saving the results of that into a <code>#Temp</code> table or a <code>@Table</code> variable, you only have to do that lookup once, then select from the result set for your update. Here is a sample using a @table variable: <pre><code>declare @OilStatus table (oilDatasetStatusID int) insert into @OilStatus select odss.oildatasetstatusid from OildataSetStatus odss join oilDataSet ods on ods.OilDataSetID = odss.OilDataSetID join SamplePoint sp on sp.SamplePointID = odss.SamplePointID join CustomerSite cs on cs.CustomerSiteID = sp.CustomerSiteID where cs.CustomerID = 2 update oildatasetstatus set oildatasetstatusid = case oildatasetstatusid WHEN 5 THEN 16 WHEN 6 THEN 17 WHEN 7 THEN 18 WHEN 8 THEN 18 WHEN 9 THEN 18 WHEN 10 THEN 19 WHEN 11 THEN 20 end where oildatasetlabstatusid in ( select oilDatasetStatusID from @OilStatus ) </code></pre> Since I do not have your exact schema, there may be errors when trying to implement the sample above but I think you will get the idea. Also, whenever multiple tables are used in a single statement try to preface every column name with an alias or the full table name. It helps keep both the sql engine and the people reading your code from getting lost.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSyntax Error
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USRob Allen
UserOwnerUserId
1. USRob Allen
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POSyntax Error
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.