# Upgraded DBAmp and the SOQL queries don't work

**URL:** <https://community.cdata.com/t/upgraded-dbamp-and-the-soql-queries-dont-work/279>\
**Category:** CData DBAmp\
**Tags:** question, salesforce, dbamp\
**Created:** [July 21, 2023, 3:18pm UTC](https://community.cdata.com/t/upgraded-dbamp-and-the-soql-queries-dont-work/279 "2023-07-21T15:18:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![shrey](https://avatars.discourse-cdn.com/v4/letter/s/b5a626/32.png) [@shrey](https://community.cdata.com/u/shrey)\
**Post date:** [July 21, 2023, 3:18pm UTC](https://community.cdata.com/t/upgraded-dbamp-and-the-soql-queries-dont-work/279/1 "2023-07-21T15:18:58Z")

</div>

We upgraded DBAMp version on our SQL Server.

Followed the instructions and created a new Linked Server.

Stored procedures are running fine, but when I execute a SOQL query; we get the following error

An invalid schema or catalog was specified for the provider “MSOLEDBSQL” for linked server “SalesForce”.

Example SOQL queries

Select \* from SalesForce…user\_\_c

Select \* from SalesForce…Account

---

<div class="post-metadata">

**Author:** ![Dani\_Moran](https://avatars.discourse-cdn.com/v4/letter/d/2acd7d/32.png) [@Dani\_Moran](https://community.cdata.com/u/Dani_Moran)\
**Post date:** [July 21, 2023, 4:39pm UTC](https://community.cdata.com/t/upgraded-dbamp-and-the-soql-queries-dont-work/279/2 "2023-07-21T16:39:28Z")

</div>

As mentioned in our release notes here: [DBAmp - Release Notes](https://cdn.cdata.com/help/AFH/dbampd/releasenotes.html#functional-changes) DBAmp v22 no longer supports the … notation. It needs a catalog of CData and a schema of Salesforce, ie

Select \* from SalesForce.CData.Salesforce.Account

---

<div class="post-metadata">

**Author:** ![shrey](https://avatars.discourse-cdn.com/v4/letter/s/b5a626/32.png) [@shrey](https://community.cdata.com/u/shrey)\
**Post date:** [July 26, 2023, 2:36pm UTC](https://community.cdata.com/t/upgraded-dbamp-and-the-soql-queries-dont-work/279/3 "2023-07-26T14:36:59Z")

</div>

Thank you. This solved the problem.
