Accessing SQL database from ArcGIS Online without ArcGIS Enterprise

[PanGIS]

Hello, 

since we are thinking of starting a project without involving ArcGIS Enterprise, our biggest concern is the access of a SQL server database (not geoenabled)

I am thinking of using:

• ArcGIS  Notebook
• Data interoperability on PRO (but this means that pro need to run al the time?))

Data pipeline seems to be unusable for this purpose.

If the two mentioned methods are both fine, do you have experience with them, what should I consider, is there any other way I could/should consider?

Thanks!

[RobertKrisher]

You can also use python to directly query databases. I would recommend using the technology that you are most comfortable with using and supporting. Using notebooks or a python script is going to have a smaller footprint in terms of licensing/installs, but using the Data Interoperability extension is going to allow you to have access to more data formats and ways of transforming the data.

[PanGIS]

Thank you @RobertKrisher ,

I tested the connection to the database in Notebooks and it works, so it is going to be the first thing I will try to do tomorrow.
ATM I need the data as is so probably I will not need Data Interoperability at all.

Question:

when I publish a  service on by referring the registered database on Enterprise I see the updates real-time every time something changes.

If I implement the Notebook, this is going to be a update (the notebook runs and only if it runs it will e.g. truncate/append), correct? I will not get a direct connection.

Thanks again!

[JakeNeedle]

Hi @PanGIS ,

How did you get the connection from Notebooks to the SQL database working? I have tried a couple of options but the connection does not seem to work.  Did you use sqlalchemy?

Thanks,

Jake

[RobertKrisher]

Depending on which tools you run the data will either be stored in memory or layers on your local machine. If you want to have a persistent representation of this data that you want to be accessible by other users you can build something into the end of your notebook to persist the results to a layer accessible by others (enterprise geodatabase, feature service, etc). When persisting the data you will need to determine whether its more effective to truncate/reload or try to incrementally update the layer with changes (the append tool can do this by upserting using the match fields parameter).