The problem typically arises when there is a discrepancy between the DSN name used and the Catalog value when setting up a linked server.
The value should correspond with the DSN employed by the SQL Gateway Service. It's important to note that SQL Gateway can only utilize System-level DSNs, so using the default User DSN created for the driver could account for the reported issue.
The default System DSN for a specific driver is CData <Data_Source_name> Sys, so that is what we need to set Catalog to. You can also fully verify the DSN to use for Catalog by going into SQL Gateway, finding the Service in use, clicking Edit on it, and then finding the value in the Data Source:
That will be the DSN in use and the same should be used for the Catalog property in SSMS. In the example above, it is the default CData MongoDB Sys DSN.
Please reach out to [email protected] if this does not solve your issue!
