Cc: gdal-dev@lists.osgeo.org; Szekeres Tamás
Subject: Re: [gdal-dev] SQL Server Driver
Jimmy,
From an examination of MSSQLSpatialTableLayer::CreateFeature() it
appears a regular INSERT statement is done for each feature written to
the db rather than any sort of bulk mechanism. I could be missing
: gdal-dev@lists.osgeo.org; Szekeres Tamás
Subject: Re: [gdal-dev] SQL Server Driver
Jimmy,
From an examination of MSSQLSpatialTableLayer::CreateFeature() it
appears a regular INSERT statement is done for each feature written to
the db rather than any sort of bulk mechanism. I could be missing
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,
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
Jimmy,
From an examination of MSSQLSpatialTableLayer::CreateFeature() it
appears a regular INSERT statement is done for each feature written to
the db rather than any sort of bulk mechanism. I could be missing
something of course. Hopefully Tamas will provide a more experienced
answer.
Best
