Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iFefT-0003I5-Vw for pgsql-admin@arkaria.postgresql.org; Wed, 02 Oct 2019 13:27:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iFefS-0003kV-A1 for pgsql-admin@arkaria.postgresql.org; Wed, 02 Oct 2019 13:27:46 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iFefR-0003kN-W3 for pgsql-admin@lists.postgresql.org; Wed, 02 Oct 2019 13:27:46 +0000 Received: from [156.26.17.12] (helo=mail0.wsutech.edu) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iFefO-0000ZW-Dt for pgsql-admin@lists.postgresql.org; Wed, 02 Oct 2019 13:27:45 +0000 X-ASG-Debug-ID: 1570022858-0b4d84267473da0001-e2Aq3s Received: from JAB-Xchg161.watc.local (JAB-Xchg161.watc.local [10.7.100.11]) by mail0.wsutech.edu with ESMTP id dRaruLv9SvC9IEUV (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NO) for ; Wed, 02 Oct 2019 08:27:38 -0500 (CDT) X-Barracuda-Envelope-From: tunderwood2@wsutech.edu Received: from JAB-Xchg161.watc.local (10.7.100.11) by JAB-Xchg161.watc.local (10.7.100.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1779.2; Wed, 2 Oct 2019 08:27:37 -0500 Received: from JAB-Xchg161.watc.local ([fe80::7d94:45d9:59a2:4637]) by JAB-Xchg161.watc.local ([fe80::7d94:45d9:59a2:4637%12]) with mapi id 15.01.1779.004; Wed, 2 Oct 2019 08:27:37 -0500 From: Tim Underwood To: "'pgsql-admin@lists.postgresql.org'" Subject: Questions regarding pgAgent and ODBC drivers Thread-Topic: Questions regarding pgAgent and ODBC drivers X-ASG-Orig-Subj: Questions regarding pgAgent and ODBC drivers Thread-Index: AdV5JHWSDdu3JUWlQ3CMO3DYsACCsw== Date: Wed, 2 Oct 2019 13:27:37 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.7.250.117] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Barracuda-Connect: JAB-Xchg161.watc.local[10.7.100.11] X-Barracuda-Start-Time: 1570022858 X-Barracuda-Encrypted: ECDHE-RSA-AES256-SHA384 X-Barracuda-URL: https://10.7.250.15:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at wsutech.edu X-Barracuda-Scan-Msg-Size: 1933 X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=3.5 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.77032 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-Host-Lookup-Failed: Reverse DNS lookup failed for 156.26.17.12 (failed) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk All, I have some general questions that aren't (so far as I can tell), specifica= lly answered by docs/wikis. Background - one of our main systems will be moving "into the cloud", and w= ill be managed as a Software as a Service (SaaS). The database will be on = PostgreSQL. The vendor will have both a live database, and a backup we can = access using pgadmin, and will be replicated from the live database every f= ew minutes or so. The replicated backup is available to us using pgadmin, = so queries can be executed, but CANNOT be stored (no write capability, so n= o Stored Procedures). We have an a couple Oracle databases, and a SQL Serv= er database. Here are my questions: pgAgent - I understand pgAgent is available for creating job schedules. Wh= at I've read seems to indicate that the pgagent schema MUST reside on the d= atabase in question (the cloud, SaaS database). Is this true? If so, we c= annot install or use it since we don't have write access to that database. Stored Procedures - as I said, we cannot save or store any procedures on th= e database itself. Read only. So, I've thought of setting up a "linked" s= erver using either Oracle or MS SQL Server, but understand the only real me= thod of linking the two would be to use the postgresql ODBC drivers? If t= hat is the case, unfortunately this probably isn't an option. The vendor h= as stated that they do not and will not support the ODBC interface. While = I know it can be setup, and might work initially, my concern is that since = they are the admins for the DB - they may change a setting or do some upgra= de which would break the ODBC connection. And - just how reliable is this = type of setup? Need to understand possibilities here, and trying to understand possible al= ternatives - we have a few stored procedures that run throughout the day, e= very day, on our on-premise database, but once it moves into the cloud - we= no longer have that access.=20