blocks|key|2940437|text|您混合了隐式联接和显式联接。这是允许的，但您需要知道如何正确地执行此操作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2940438|问题是，显式连接(使用JOIN关键字实现的连接)优先于隐式连接(“逗号”连接，其中连接条件在WHERE子句中指定)。|offset|length|style|CODE|2940439|下面是您的查询的概要：|2940440|SELECT
++…
FROM+a,+b+LEFT+JOIN+dkcd+ON+…
WHERE+…|code-block|syntax|javascript|2940441|您可能希望它的行为是这样的：|2940442|SELECT
++…
FROM+(a,+b)+LEFT+JOIN+dkcd+ON+…
WHERE+…|2940443|也就是说，表a和b的组合与表dkcd连接。实际上，正在发生的事情是|2940444|SELECT
++…
FROM+a,+(b+LEFT+JOIN+dkcd+ON+…)
WHERE+…|2940445|也就是说，正如您可能已经理解的那样，dkcd是专门针对b且仅针对b进行联接的，然后联接的结果将与a组合，并使用WHERE子句进一步过滤。在这种情况下，ON子句中对a的任何引用都是无效的，此时a是未知的。这就是您收到错误消息的原因。|2940446|如果我是你，我可能会尝试重写这个查询，一个可能的解决方案可能是：|2940447|SELECT+DISTINCT
++a.maxa,
++b.mahuyen,
++a.tenxa,
++b.tenhuyen,
++ISNULL(dkcd.tong,+0)+AS+tongdkcd
FROM+phuongxa+a
++INNER+JOIN+quanhuyen+b+ON+LEFT(a.maxa,+2)+=+b.mahuyen
++LEFT+OUTER+JOIN+(
++++SELECT
++++++maxa,
++++++COUNT(*)+AS+tong
++++FROM+khaosat
++++WHERE+CONVERT(datetime,+ngaylap,+103)+BETWEEN+'Sep+1+2011'+AND+'Sep+5+2011'
++++GROUP+BY+maxa
++)+AS+dkcd+ON+dkcd.maxa+=+a.maxa
WHERE+a.maxa+<>+'99'
ORDER+BY+a.maxa|2940448|在这里，首先连接表a和b，然后将结果连接到dkcd。基本上，这是与您的查询相同的查询，只是对其中一个连接使用了不同的语法，这产生了很大的不同：dkcd的连接条件中的引用a.maxa现在绝对有效。|2940449|正如@Aaron+Bertrand正确指出的那样，您可能应该在ORDER+BY子句中使用特定的别名来限定maxa，可能是a。|2940450|entityMap^0|0|B|4|1A|5|0|0|0|0|0|6|1|8|1|E|4|0|0|I|4|R|1|W|1|1C|1|1J|5|23|2|29|1|2N|1|0|0|0|9|1|B|1|L|4|1Z|4|2C|6|0|V|8|1G|4|1O|1|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@$D|1A|E|1B|F|G]|$D|1C|E|1D|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1E|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1F|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1G|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|1H|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|1I|8|@$D|1J|E|1K|F|G]|$D|1L|E|1M|F|G]|$D|1N|E|1O|F|G]]|9|@]|A|$]]|$1|U|3|V|5|L|7|1P|8|@]|9|@]|A|$M|N]]|$1|W|3|X|5|6|7|1Q|8|@$D|1R|E|1S|F|G]|$D|1T|E|1U|F|G]|$D|1V|E|1W|F|G]|$D|1X|E|1Y|F|G]|$D|1Z|E|20|F|G]|$D|21|E|22|F|G]|$D|23|E|24|F|G]|$D|25|E|26|F|G]]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|27|8|@]|9|@]|A|$]]|$1|10|3|11|5|L|7|28|8|@]|9|@]|A|$M|N]]|$1|12|3|13|5|6|7|29|8|@$D|2A|E|2B|F|G]|$D|2C|E|2D|F|G]|$D|2E|E|2F|F|G]|$D|2G|E|2H|F|G]|$D|2I|E|2J|F|G]]|9|@]|A|$]]|$1|14|3|15|5|6|7|2K|8|@$D|2L|E|2M|F|G]|$D|2N|E|2O|F|G]|$D|2P|E|2Q|F|G]]|9|@]|A|$]]|$1|16|3|-4|5|6|7|2R|8|@]|9|@]|A|$]]]|17|$]]

You are mixing implicit joins with explicit joins. That is allowed, but you need to be aware of how to do that properly.

The thing is, explicit joins (the ones that are implemented using the <code>JOIN</code> keyword) take precedence over implicit ones (the 'comma' joins, where the join condition is specified in the <code>WHERE</code> clause).

Here's an outline of your query:

<pre><code>SELECT
 …
FROM a, b LEFT JOIN dkcd ON …
WHERE …
</code></pre>

You are probably expecting it to behave like this:

<pre><code>SELECT
 …
FROM (a, b) LEFT JOIN dkcd ON …
WHERE …
</code></pre>

that is, the combination of tables <code>a</code> and <code>b</code> is joined with the table <code>dkcd</code>. In fact, what's happening is

<pre><code>SELECT
 …
FROM a, (b LEFT JOIN dkcd ON …)
WHERE …
</code></pre>

that is, as you may already have understood, <code>dkcd</code> is joined specifically against <code>b</code> and only <code>b</code>, then the result of the join is combined with <code>a</code> and filtered further with the <code>WHERE</code> clause. In this case, any reference to <code>a</code> in the <code>ON</code> clause is invalid, <code>a</code> is unknown at that point. That is why you are getting the error message.

If I were you, I would probably try to rewrite this query, and one possible solution might be:

<pre><code>SELECT DISTINCT
 a.maxa,
 b.mahuyen,
 a.tenxa,
 b.tenhuyen,
 ISNULL(dkcd.tong, 0) AS tongdkcd
FROM phuongxa a
 INNER JOIN quanhuyen b ON LEFT(a.maxa, 2) = b.mahuyen
 LEFT OUTER JOIN (
 SELECT
 maxa,
 COUNT(*) AS tong
 FROM khaosat
 WHERE CONVERT(datetime, ngaylap, 103) BETWEEN 'Sep 1 2011' AND 'Sep 5 2011'
 GROUP BY maxa
 ) AS dkcd ON dkcd.maxa = a.maxa
WHERE a.maxa &lt;&gt; '99'
ORDER BY a.maxa
</code></pre>

Here the tables <code>a</code> and <code>b</code> are joined first, then the result is joined to <code>dkcd</code>. Basically, this is the same query as yours, only using a different syntax for one of the joins, which makes a great difference: the reference <code>a.maxa</code> in the <code>dkcd</code>'s join condition is now absolutely valid.

As @Aaron Bertrand has correctly noted, you should probably qualify <code>maxa</code> with a specific alias, probably <code>a</code>, in the <code>ORDER BY</code> clause.

blocks|key|253617|text|有时，当您在查询中以错误的方式使用架构(dbo)时，就会出现此错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|253618|例如，如果你这样写：|253619|select+dbo.prd.name
from+dbo.product+prd|code-block|syntax|javascript|253620|您将得到错误。|253621|在这种情况下，请将其更改为：|253622|select+prd.name
from+dbo.product+prd|253623|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|V|8|@]|9|@]|A|$G|H]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Sometimes this error occurs when you use your schema (dbo) in your query in a wrong way.

for example if you write:

<pre><code>select dbo.prd.name
from dbo.product prd
</code></pre>

you will get the error.

In this situations change it to:

<pre><code>select prd.name
from dbo.product prd
</code></pre>

blocks|key|3154803|text|我是SQL的新手，但在我参加的一门课程中遇到了这个问题，我发现将查询分配给项目特别有助于消除多部分错误。例如，我创建的项目是CTU+SQL+project，所以我确保我的脚本以USE+CTU+SQL+Project作为我的第一行，如下所示。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3154804|USE+[CTU+SQL+Project]
SELECT+Advisors.First_Name,+Advisors.Last_Name...and+so+on.|code-block|syntax|javascript|3154805|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I'm new to SQL, but came across this issue in a course I was taking and found that assigning the query to the project specifically helped to eliminate the multi-part error. For example the project I created was CTU SQL Project so I made sure I started my script with USE [CTU SQL Project] as my first line like below.

<pre><code>USE [CTU SQL Project]
SELECT Advisors.First_Name, Advisors.Last_Name...and so on.
</code></pre>

blocks|key|3154834|text|如果此错误发生在UPDATE中，请仔细检查表中包含导致错误的列/字段的JOIN。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3154835|在我的例子中，这是由于缺少JOIN本身，它由于一个未知字段(如Andriy+pointed+out)而生成相同的错误。|3154836|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/7314936/6225838^0|8|6|Z|4|0|D|4|V|I|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|H|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

If this error happens in an <code>UPDATE</code>, double-check the <code>JOIN</code> on the table with the column/field that is causing the error.

In my case this was due to the lack of the <code>JOIN</code> itself, which generated the same error due to an unknown field (as <a href="https://stackoverflow.com/a/7314936/6225838">Andriy pointed out</a>).

blocks|key|253671|text|相反，您可以尝试连接表，如|type|unstyled|depth|inlineStyleRanges|entityRanges|data|253672|select+
++....+
from+
+++dkcd+
+++++right+join+
++++++++++++++++a
++++++++++++++++++,+b|code-block|syntax|javascript|253673|这应该是可行的|253674|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Instead you can try joining tables like,

<pre><code>select 
 .... 
from 
 dkcd 
 right join 
 a
 , b
</code></pre>

This should work

blocks|key|258625|text|如果您已指定alies名称，请将其更改为实际名称|type|unstyled|depth|inlineStyleRanges|entityRanges|data|258626|例如|258627|SELECT++
++++A.name,A.date
++FROM+[LoginInfo].[dbo].[TableA]+as+A
+++join+
++[LoginInfo].[dbo].[TableA]+as+B+
++on++[LoginInfo].[dbo].[TableA].name=[LoginInfo].[dbo].[TableB].name;|code-block|syntax|javascript|258628|将其更改为|258629|SELECT++
++++A.name,A.date
++FROM+[LoginInfo].[dbo].[TableA]+as+A
+++join+
++[LoginInfo].[dbo].[TableA]+as+B+
++on++A.name=B.name;|258630|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

if you have given alies name change that to actual name 

for example

<pre><code>SELECT 
 A.name,A.date
 FROM [LoginInfo].[dbo].[TableA] as A
 join 
 [LoginInfo].[dbo].[TableA] as B 
 on [LoginInfo].[dbo].[TableA].name=[LoginInfo].[dbo].[TableB].name;
</code></pre>

change that to 

<pre><code>SELECT 
 A.name,A.date
 FROM [LoginInfo].[dbo].[TableA] as A
 join 
 [LoginInfo].[dbo].[TableA] as B 
 on A.name=B.name;
</code></pre>

blocks|key|255378|text|SELECT+DISTINCT
++++++++phuongxa.maxa+,
++++++++quanhuyen.mahuyen+,
++++++++phuongxa.tenxa+,
++++++++quanhuyen.tenhuyen+,
++++++++ISNULL(dkcd.tong,+0)+AS+tongdkcd
FROM++++phuongxa+,
++++++++quanhuyen
++++++++LEFT+OUTER+JOIN+(+SELECT++++khaosat.maxa+,
++++++++++++++++++++++++++++++++++++COUNT(*)+AS+tong
++++++++++++++++++++++++++FROM++++++khaosat
++++++++++++++++++++++++++WHERE+++++CONVERT(DATETIME,+ngaylap,+103)+BETWEEN+'Sep+1+2011'
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++AND
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++'Sep+5+2011'
++++++++++++++++++++++++++GROUP+BY++khaosat.maxa
++++++++++++++++++++++++)+AS+dkcd+ON+dkcd.maxa+=+maxa
WHERE+++phuongxa.maxa+<>+'99'
++++++++AND+LEFT(phuongxa.maxa,+2)+=+quanhuyen.mahuyen
ORDER+BY+maxa;|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|255379|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>SELECT DISTINCT
 phuongxa.maxa ,
 quanhuyen.mahuyen ,
 phuongxa.tenxa ,
 quanhuyen.tenhuyen ,
 ISNULL(dkcd.tong, 0) AS tongdkcd
FROM phuongxa ,
 quanhuyen
 LEFT OUTER JOIN ( SELECT khaosat.maxa ,
 COUNT(*) AS tong
 FROM khaosat
 WHERE CONVERT(DATETIME, ngaylap, 103) BETWEEN 'Sep 1 2011'
 AND
 'Sep 5 2011'
 GROUP BY khaosat.maxa
 ) AS dkcd ON dkcd.maxa = maxa
WHERE phuongxa.maxa &lt;&gt; '99'
 AND LEFT(phuongxa.maxa, 2) = quanhuyen.mahuyen
ORDER BY maxa;
</code></pre>

blocks|key|253697|text|我在SQL+SERVER中遇到了同样的错误消息，因为我有多个连接，所以更改连接的顺序为我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|253698|entityMap^0|14|C|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I was struggling with the same error message in SQL SERVER, since I had multiple joins, changing the order of the joins solved it for me.

blocks|key|258667|text|我的错误是使用了表中不存在的字段。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|258668|table1.field1+=>不存在|258669|table2.field1+=>正确|258670|更正您的表名。|offset|length|style|BOLD|258671|我的错误是由于使用WITH而发生的|258672|WITH+RCTE+AS+(
+++SELECT...
)
SELECT+RCTE.Name,+...
FROM+
++RCTE+INNER+JOIN+Customer
++ON+RCTE.CustomerID+=+Customer.ID+|code-block|syntax|javascript|258673|在与其他表的联接中使用...|258674|entityMap^0|0|0|0|0|7|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Z|8|@$H|10|I|11|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|12|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|13|8|@]|9|@]|A|$Q|R]]|$1|S|3|T|5|6|7|14|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

My error was to use a field that did not exist in table.

table1.field1 => is not exist

table2.field1 => is correct

Correct your Table Name.

my error occurred because of using WITH

<pre><code>WITH RCTE AS (
 SELECT...
)
SELECT RCTE.Name, ...
FROM 
 RCTE INNER JOIN Customer
 ON RCTE.CustomerID = Customer.ID 
</code></pre>

when used in join with other tables ...

blocks|key|2940629|text|你是不是忘了加入一些表了？如果不是，那么您可能需要使用一些别名。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2940630|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Did you forget to join some tables? If not then you probably need to use some aliases.

blocks|key|2940672|text|我在JDBC中也遇到了同样的错误。我检查了所有东西，我的查询是正确的。事实证明，在where子句中，我有一个论点：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2940673|where+s.some_column+=+?|code-block|syntax|javascript|2940674|而我传入的参数的值是空的。这也给出了同样的错误，这是误导性的，因为当你在互联网上搜索时，你最终会发现查询结构有问题，但我的情况并非如此。只是觉得有人可能会面临同样的问题|2940675|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I was having the same error from JDBC. Checked everything and my query was fine. Turned out, in where clause I have an argument:

<pre><code>where s.some_column = ?
</code></pre>

And the value of the argument I was passing in was null. This also gives the same error which is misleading because when you search the internet you end up that something is wrong with the query structure but it's not in my case. Just thought someone may face the same issue

blocks|key|257699|text|在我的例子中，问题是我为表指定的别名。"oa“似乎不适用于SQL+Server。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|257700|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case the issue turned out to be the alias name I had given to the table. "oa" seems to be not acceptable for SQL Server.

blocks|key|3155095|text|我也在与这个错误作斗争，最终得到了与答案相同的策略。我附上我的答案只是为了确认这是一个应该有效的策略。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3155096|下面是一个示例，我首先在两个表之间执行一次内部连接，我知道这两个表获得了数据，然后在可能具有可能为空的相应行的表上进行了两次左外部连接。您可以混合使用内部连接和外部连接来获得数据交叉表的结果，而不是在表之间执行默认的逗号分隔语法，并在所需的连接中遗漏行。|3155097|use+somedatabase
go+

select+o.operationid,+o.operatingdate,+p.pasid,+p.name+as+patientname,+o.operationalunitid,+f.name+as+operasjonsprogram,++o.theaterid+as+stueid,+t.name+as+stuenavn,+o.status+as+operasjonsstatus+from+operation+o+
inner+join+patient+p+on+o.operationid+=+p.operationid+
left+outer+join+freshorganizationalunit+f+on+f.freshorganizationalunitid+=+o.operationalunitid
left+outer+join+theater+t+on+t.theaterid+=+o.theaterid
where+(p.Name+like+'%25Male[0-9]%25'+or+p.Name+like+'%25KFemale+[0-9]%25')|code-block|syntax|javascript|3155098|首先:在希望进行数据匹配的表之间进行内部连接。第二部分:继续外部连接，尝试检索其他表中的数据，但是如果表外部连接to没有获得相应的数据，或者没有与您在on谓词/条件中设置的条件匹配，这将不会过滤出您的结果集。|3155099|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I was also struggling with this error and ended up with the same strategy as the answer. I am including my answer just to confirm that this is a strategy that should work. 

Here is an example where I do first one inner join between two tables I know got data and then two left outer joins on tables that might have corresponding rows that can be empty. You mix inner joins and outer joins to get results with data accross tables instead of doing the default comma separated syntax between tables and miss out rows in your desired join. 

<pre><code>use somedatabase
go 

select o.operationid, o.operatingdate, p.pasid, p.name as patientname, o.operationalunitid, f.name as operasjonsprogram, o.theaterid as stueid, t.name as stuenavn, o.status as operasjonsstatus from operation o 
inner join patient p on o.operationid = p.operationid 
left outer join freshorganizationalunit f on f.freshorganizationalunitid = o.operationalunitid
left outer join theater t on t.theaterid = o.theaterid
where (p.Name like '%Male[0-9]%' or p.Name like '%KFemale [0-9]%')
</code></pre>

First: Do the inner joins between tables you expect to have data matching. 
Second part: Continue with outer joins to try to retrieve data in other tables, 
but this will not filter out your result set if table outer joining to has not got corresponding data or match on the condition you set up in the on predicate / condition.

blocks|key|2940797|text|对我起作用的是将WHERE子句更改为SELECT子查询|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2940798|发自：|2940799|++++DELETE+FROM+CommentTag+WHERE+[dbo].CommentTag.NoteId+=+[dbo].FetchedTagTransferData.IssueId|code-block|syntax|javascript|2940800|至：|2940801|++++DELETE+FROM+CommentTag+WHERE+[dbo].CommentTag.NoteId+=+(SELECT+NoteId+FROM+FetchedTagTransferData)|2940802|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

What worked for me was to change my WHERE clause into a SELECT subquery

FROM:

<pre><code> DELETE FROM CommentTag WHERE [dbo].CommentTag.NoteId = [dbo].FetchedTagTransferData.IssueId
</code></pre>

TO:

<pre><code> DELETE FROM CommentTag WHERE [dbo].CommentTag.NoteId = (SELECT NoteId FROM FetchedTagTransferData)
</code></pre>

blocks|key|255510|text|此错误也可能是由于SELECT语句中的列名之间缺少逗号,而导致的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|255511|例如：|255512|SELECT+MyCol1,+MyCol2+MyCol3+FROM+SomeTable;|code-block|syntax|javascript|255513|entityMap^0|R|1|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|S|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

This error can also be caused by simply missing a comma <code>,</code> between the column names in the SELECT statement. 

eg:

<pre><code>SELECT MyCol1, MyCol2 MyCol3 FROM SomeTable;
</code></pre>

blocks|key|253809|text|对我来说，问题是我愚蠢地调用了一个没有空括号的select+[apo].[GenerateNationalIdFrance]而不是select+[apo].[GenerateNationalIdFrance]()的DB函数……我花了几分钟才意识到这一点，但值得一提的是，对于那些初学者来说:-)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|253810|entityMap^0|N|13|1T|15|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

For me the issue was that I was stupidly calling a DB function without empty brackets <code>select [apo].[GenerateNationalIdFrance]</code> instead of <code>select [apo].[GenerateNationalIdFrance]()</code> ... took me few minutes to realize that but worth mentioning for juniors out there :-)

blocks|key|255572|text|对我来说，我使用了错误的别名拼写，正确的拼写后它就可以工作了|type|unstyled|depth|inlineStyleRanges|entityRanges|data|255573|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For me I was using wrong alias spellings , it worked after correct spelings

I've seen similar errors on SO, but I don't find a solution for my problem.
I have a SQL query like:

<pre><code>SELECT DISTINCT
 a.maxa ,
 b.mahuyen ,
 a.tenxa ,
 b.tenhuyen ,
 ISNULL(dkcd.tong, 0) AS tongdkcd
FROM phuongxa a ,
 quanhuyen b
 LEFT OUTER JOIN ( SELECT maxa ,
 COUNT(*) AS tong
 FROM khaosat
 WHERE CONVERT(DATETIME, ngaylap, 103) BETWEEN 'Sep 1 2011'
 AND
 'Sep 5 2011'
 GROUP BY maxa
 ) AS dkcd ON dkcd.maxa = a.maxa
WHERE a.maxa &lt;&gt; '99'
 AND LEFT(a.maxa, 2) = b.mahuyen
ORDER BY maxa;
</code></pre>

When I execute this query, the error result is:
The multi-part identifier "a.maxa" could not be bound. Why?
 
P/s: if i divide the query into 2 individual query, it run ok.

<pre><code>SELECT DISTINCT
 a.maxa ,
 b.mahuyen ,
 a.tenxa ,
 b.tenhuyen
FROM phuongxa a ,
 quanhuyen b
WHERE a.maxa &lt;&gt; '99'
 AND LEFT(a.maxa, 2) = b.mahuyen
ORDER BY maxa;
</code></pre>

and

<pre><code>SELECT maxa ,
 COUNT(*) AS tong
FROM khaosat
WHERE CONVERT(DATETIME, ngaylap, 103) BETWEEN 'Sep 1 2011'
 AND 'Sep 5 2011'
GROUP BY maxa;
</code></pre>

The multi-part identifier could not be bound

SQL Server

我在SO上看到过类似的错误，但我没有找到解决问题的方法。我有一个SQL查询，如：SELECT DISTINCT        a.maxa ,        b.mahuyen ,        a.tenxa ,        b.tenhuyen ,        ISNULL(dkcd.tong, 0) AS t...

问无法绑定多部分标识符
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法绑定多部分标识符EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法绑定多部分标识符
EN