Lynn Pettis (7/24/2014)
One thing to remember about Oracle and SQL Server, they are not the same. The internals are different, and there for how the operate is different.For example, the following will work fine in SQL Server but will fail in Oracle:
select current_timestamp
To get that SQL to run in Oracle it needs to be written as this:
select current_timestamp from dual
I'll leave it to you to find out what dual is in Oracle.
Actually in Oracle it must be written as:
select current_timestamp from dual;
Oracle absolutely requires the ending ; before it will run a query. As to "dual", Oracle's parser requires a FROM clause after a SELECT, so Oracle create a dummy (pseudo-)table to use when the SELECT doesn't pull data from an actual table.
I'm sure not what only 1,000 rows is going to tell you, but, as noted by others, to be fair to SQL Server, explicitly start a transaction before any insert, then explicitly commit it afterward. The 1000 separate transactions are huge overhead vs. a single, larger trans.
SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.