On Tue, 18 Jul 2000, Alex Bolenok wrote:
> You should use System DSN (so that SQL Server, that runs under either
> LOCALSYSTEM or .\SQLExecutive account, can see it).
This is the trick to get the PostgreSQL driver into the list.
Thanks for the hint.
> Add a DSN, then configure a Subscriber (use ODBC subscriber). It must appear
> in your subscribers list. (I cannot repoduce all the actions needed, because
> I have no MS SQL Server installed handy, but it _did_ work on my Windows
> 2000 Server / MS SQL Server 7.0 (full version) / PostgreSQL 6.5.4 / RedHat
> 6.1 configuration).
Is there any possibility to test the connection to the driver. I've got
it included into the list of subscribers but after the configuration
or after setting the properties I get the following error message:
"SQL Server Enterprise Manager konnte nicht überprüfen, ob 'PostgreSQL'
ein gültiger Datenquellenname ist.
Möchten Sie ihn trotzdem als Abonnenten aktivieren?
Fehler 21076: [SQL-DMO] Die angegebene DSN-Informationen sind falsch
oder unvollständig."
Trial of a translation:
"SQL Server Enterprise Manager couldn't check, if 'PostgreSQL'
is a valid data source name.
Do you want it to be a subscriber anyway?
Error 21076: [SQL-DMO] The DSN-informations are invalid or not
complete."
When creating the DSN I just unchecked the "Readonly"-fields and
filled in the appropriate login user information.
If I restart the subscriber properties menu the PostgreSQL entry
vanished (for sure because of the error).
> If you fail to set up an ODBC Subscriber, you may still try to set up an OLE
> DB Subsriber. First create a linked server (use OLE DB for ODBC) and insert
> either DSN or provider string into the corresponding field. Then if you
Sorry but I havn't found a way to set up such a beast. Could you explain
shortly how to do that or give a pointer to the related description?
Thanks for your detailed help
Andreas.
