[Last Call] Learn how to a build a cloud-first strategyRegister Now

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

Missing Join Predicate SQL2005

I'm getting a Missing Join Predicate (W2K3/SP1 SQL2005 ) in a trace generated by the system (C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG), how to find out what querry is causing it?
0
feiza
Asked:
feiza
  • 2
  • 2
1 Solution
 
Aneesh RetnakaranDatabase AdministratorCommented:
Did you try running the trace ?
0
 
feizaAuthor Commented:
Yes and nothing have show up so far, but in other systems we have the same issue, auto generated traces with Missing Join Predicate
0
 
imran_fastCommented:
Missing Join Predicate: Indicates whether or not the query in question has a join predicate. If not, this can cause the Query Optimizer to produce a less than optimized query plan. To fix this, add a join predicate.

Run sql profiler to identify this query.
0
 
feizaAuthor Commented:
I have ran SQL profiler for hours and nothing show up in this trace, now it show up in a trace than I presume is been autogenerated by SQL, any ideas?...
thanks
0
 
imran_fastCommented:
hi feiza,
Its more like a warning ..
0

Featured Post

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.

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