In general the ole db provider for sql server is
fastest. But in some situations I think the ole db
provider for odbc is faster. Best bet is to try both and
test!
Sincerely,
Invotion Engineering Team
Advanced Microsoft Hosting Solutions
http://www.Invotion.com
>--Original Message--
>Hi,
>I'm trying to access a MS SQL Server db
>from a CGI (pure C program).
>Which is the most efficient (fast, incl. fetching
>many records on a search term) ...using
>embedded SQL in C, ODBC or any other methods?
>Any suggestions?
>Jon
>.
>Thanks.
"Invotion" <anonymous@.discussions.microsoft.com> wrote in message news:<1520b01c3fa36$d4a1f
e30$a401280a@.phx.gbl>...
> In general the ole db provider for sql server is
> fastest. But in some situations I think the ole db
> provider for odbc is faster. Best bet is to try both and
> test!
> Sincerely,
> Invotion Engineering Team
> Advanced Microsoft Hosting Solutions
> http://www.Invotion.com
>
Showing posts with label ole. Show all posts
Showing posts with label ole. Show all posts
Friday, March 30, 2012
newbie question on SQL Server, ODBC
Newbie question for SQL Server System Integration Services Flat File Import
I am new to SSIS...
I have a very simple package that has a flat file source object and an ole db destination object in the data flow. All works fine.
If I change a row in the flat file to make it fail how do I make the program continue and go to the next row?
The ole db destination does not have a Error Output properties like the flat file source does.
Thanks
Check the Properties of the Data Flow Task (or other task you're using for dealing with the flat file) in the Control Flow tab, there is an attribute MaximumErrorCount, which is default to 1.
Subscribe to:
Posts (Atom)