Thanks to everyone who took the time to respond. I am not worried about the original execution time of 15 mins. The script migrates data from an old...

If the update works properly in the new 2005 environment, but not in the old 2000 environment I would take a practical approach and move everything to 2005. Then...

Which compatibility level are you running on the 2005 database?

Cheers,

Win

When you re-write your procedure use "execute immediate" and not package dbms_sql. This package is very powerful, but syntactically a nightmare.

Also, you cannot issue a select statement inside a...

I cannot judge whether your circular relationship between tables 1 and 2 is a good thing. To stop the recursion I would use Noeld's construct, but with function trigger_nestlevel(...

You can also test the trigger recursion with function trigger_nestlevel (see BOL) and stop recursion when the nest level exceeds 0. This method is specific to 1 trigger...

Tried and failed. The string can evaluate to something like this:

BLACKADDER\SS2KCS.1Day.dbo.sp_helpsort

Cheers,

Win

Simon,

Your first half tag appears to point to the same document.  I can't get to Part 1, A - O from there.

Win

It would be nice to merge the best of breed from both languages. 

How much longer will it take Oracle to replace dbms_output.put_line with a simple PRINT statement that has...

sql svr ist not as fast in cursor mode as oracle, but cursing through a loop n times calling 15 procedures (is that your plan?) should not be significantly slower.

sql...

I have implemented 2 tracking systems, which track changes of drillhole information in a mining-related data management system.  The 2 systems share some code, but operate independantly. Record tracking, when...

We use @@trancount just as boundary marker in cascading transactions. The auditing trigger in a child table starts like this:

   if @@trancount > 1

      return

A transaction count greater than 1...

DBCC OPENTRAN  will give you information about the oldest active transaction.  However, if you are looking to identify the start/end of a transaction in PL/SQL using DBMS_TRANSACTION.local_transaction_id you'll have to re-think...

There's another subtle difference about varchars.  The maximum field width is 4000 as you mentioned, but the declaration of a varchar variable in PL/SQL can be as large as 32767...

Sql Server 7 ( if I remember correctly) had a problem creating a temp table inside a procedure.  Select into ..where 1=2 was the only way to get around this...