# How do I know where in my SQL errors are?

It jus says something like "error at position: 4352" but there's no way to know where that position is in my code

##### Post Metadata
- Posted at: over 6 years ago
- Author title: Data Analyst
- Net upvotes: 1


## Comments
### Comment 1

Hey Carlos! 

I'm Izzy, the Looker Community manager. Yeah, especially in huge SQL queries it can be hard to figure out exactly where the issue lies. That error that pops up on explores doesn't help, since like you said, you don't know where that position is.

If you open the offending query in SQL runner (Via the SQL tab near the results) and run it there, when it fails you will be able to scroll through the query and find the issue highlighted with a red X on the side of the window. It's not ALWAYS the exact place you need to fix something, but it's usually close and can be extremely helpful. 

In the future, you can also post questions like this on the Looker Community forums— https://www.discourse.looker.com, it's full of other Looker users and more lively than the G2 comment section.

##### Comment Metadata
- Posted at: over 6 years ago
- Net upvotes: 1



## Related Product
[Looker](https://www.g2.com/products/looker/reviews)

## Related Category
[Analytics Platforms](https://www.g2.com/categories/analytics-platforms)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: almost 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: almost 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: almost 13 years ago
  - Comments: 4