I have a Powershell script that loops through a database and outputs the spatial tables into another database in GDA2020 datum. I see one particular table is outputting but is empty. This table should have over 330000 rows. Is there a limit of rows OGR can handle or is there something I can add to the script to handle this, or could it be due to this table having multiple geometry types. Here is the script in OGR to make it clearer.
ogr2ogr -s_srs "+proj=utm +zone=55 +south +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs +wktext +nadgrids=C:\Program Files\MapManager35\ProjLib\GDA94_GDA2020_conformal.gsb" -t_srs "+proj=utm +zone=55 +south +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs +wktext" -f "MSSQLSPATIAL" "MSSQL:driver={SQL Server Native Client 11.0};Server=blahblah;Database=DestinationTable;Trusted_Connection=Yes" "MSSQL:driver={SQL Server Native Client 11.0};Server=blahblah;Tables=dbo.SourceTable;Database=blahblah;Trusted_Connection=Yes" -nln outputtable
ogrinfo
work for that table? what does it show?-makevalid
option on ogr2ogr gdal.org/programs/ogr2ogr.html is not limited to any file format so it should work.