Re: sql server i/o bottle neck ?
It's hard to explain the I/O disparity without knowing the details of your
job. My first guess is that you might be committing each SQL Server insert
(default is autocommit) but not each Oracle insert (default is implicit
transactions on). This would require SQL Sever to perform many more
transaction log writes.
Can you explain this paragraph a little more. I'm not a java guy.
Thanks for your help.
.
Relevant Pages
- Re: ADO.NET Transaction
... The SqlBulkCopy class can take anything you can expose with a DataReader and send it to SQL Server in a single high-speed operation. ... Hitchhiker's Guide to Visual Studio and SQL Server ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ... Client transactions put too much schema-dependent, ...
(microsoft.public.dotnet.framework.adonet) - Re: ADO.NET Transaction
... Hitchhiker's Guide to Visual Studio and SQL Server ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ... Is it always a bad reason to do client transactions? ...
(microsoft.public.dotnet.framework.adonet) - Re: ADO.NET Transaction
... Hitchhiker's Guide to Visual Studio and SQL Server ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ... Client transactions put too much schema-dependent, ...
(microsoft.public.dotnet.framework.adonet) - Re: Rows not transferring
... Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) ... So I fixed that by adding the connection properties ... > transactions or failed when attempting to join. ...
(microsoft.public.sqlserver.dts) - Re: Tables, ranges, filters and speed
... Use a query statement instead, better yet, write a stored procedure on your SQL server do the hard work, thats what they are built for. ... I am currently using the TTable.Filter to select only the transactions ... for a particular terminal then I use a manual range on the dates to ... Should I just use a range of dates and terminals? ...
(alt.comp.lang.borland-delphi) |
|
