Sometimes its a bit difficult to find old, official documentations - but luckily I have just came across with ArcGIS Diagrammer doco's from ESRI in PDF. I uploaded it to my personal AWS drive as these files can easily come and go from and to sites, old websites disappear, etc.
You can download it here:
First let's export a table to the file system:
pg_dump --host localhost --port 5432 --username mypgusername --format plain --verbose --file /var/lib/pgsql/stations.sql --table mypgschamename.mypgtablename mydatabasename
Now we have a sql file on filesystem - ready to be migrated.
We can do that even for a remote PG server:
psql -h 111.111.111.111 -p 5432 -d mydbname -U myusername -W -f stations.sql
After putting in the password for the remote server the restore takes place over the wire.
On WAN network it might be slow and can disconnect occasionally - I'd say several hundred of MB table still can easily be restored like this.
In the last few years/months we have been trying to formulate our new business strategy - and we seemingly get to the point where we can safely say we have some good ideas to implement.
Our new website layout is now trying to correspond to this endeavour. So if you like to see what we are up to these days please visit mapcortex.com.
This is the lates issue I have come accross with. The Microsoft.SqlServer.Types spatial library doens't seem to playing well in Console and Desktop C# applications - they do work ok in Web Applications though.
My workaround is to use the 10.50.1600.1 version of the dll.
This is what I have just encountered today. When I add the second parameter to the arcpy.Copy_management toolbox the actual filename must not contain point characters (which is related to schema names).
So for instance, if you try to copy a mosaic dataset from r"d:\SDEConnections\myconnection.sde\super.data.mymosaic_dataset" to a location of r"d:\tempfgdb\super.data.mymosaic_dataset" after running this toolbox you will end up with a copied mosaic dataset in your destination but without schmea names - in this case this would be r"d:\tempfgdb\mymosaic_dataset".
Solution/workaround is - don't try to copy schema names.
Good question, isn't it? ESRI decided that you will not be able to connect to an ArcSDE instance from ArcMap 10.7 onwards. Its a way too old architecture, so it should be revised and deprecated in favour of the same product that is wrapped into a different framework.
ITs a bit of a shame if your corporate architecture has multiple running instances - seems like you will be spending a lot of money to replace this if you want to enable users to connect to the database via this engine.
What is going to be the next ESRI? Deprecating the database connection tools only allowing your fancy cloud datastore or something similar? Or even better - no database conenction should be allowed from ESRI at all!!! Either you connect to a ArcGIS service or buzz off.
Now you have to pay me for this good idea...
