Hi, Assuming you refer to the MSSQL driver the driver should provide fast data retrieval, but hasn't yet been optimized to provide fast data upload. Currently the MSSQL driver use WKT for the geometries when submitting data to the server, while when retrieving data we use the native SqlGeometry/SqlGeography serialization format.
Not sure what you mean by "do not do bulk insert". How your own routine is looking like? Is this a .NET based program (using SqlGeometry by default)? Best regards, Tamas 2012/8/25 Duchesne, Jimmy <[email protected]> > Hello,**** > > ** ** > > I’ve been using SQL Server Driver for a few days now, and I noticed it was > very slow, whatever the parameters, such as GT, I was using.**** > > ** ** > > I need to insert millions of rows in a table.**** > > ** ** > > To give you an idea, it takes around 1 minute to import 10k records with > the driver**** > > ** ** > > On the other hand, if I write my own routine which reads a MapInfo file > and does batch insert into the database, I can insert over 125k records per > minute.**** > > ** ** > > I tried reading the same TAB file with ogr2ogr but writing to PostGis and > noticed the speed was about the same than my routine, which is enough for > my needs.**** > > ** ** > > Would it be possible that the SQL Server Driver does not do bulk insert?** > ** > > ** ** > > Thanks for the help.**** > > ** ** > > *Jimmy Duchesne *** > > ** ** > > _______________________________________________ > gdal-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/gdal-dev >
_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
