You'd have to use an INSTEAD OF trigger, naturally. Those are a pain to write and maintain, since you must write code yourself to complete the modification -- DELETE...

Yes, the logging especially will be take a lot of time.

But, it will be much more bearable if:

1) the child tables are clustered properly (as usual!), i.e., starting with...

I'd definitely add a bit column to the table. Your data and your statements seem contradictory, but I think when a new row is added that becomes current, you...

MyDoggieJessie (3/6/2014)

---

This should work for you (create a variable and set the @@ERROR to it, then test for it before you attempt the xp_cmdshell)DECLARE @Err INT

BEGIN TRY

BEGIN TRANSACTION

<A whole bunch...

If the original amount is odd, add 1 cent to the first joint account holder. That will work regardless of the number of joint account holders:

select cast(original_amount/2 +

...

The core thing is not to skimp on the design. It may look 'leaner' to just leave out some relationship tables, or to combine some relationship tables, but doing...

halifaxdal (2/21/2014)

---

ScottPletcher (2/21/2014)

---

I, too, got different totals; mine add up to 82, the number of sample rows of data.

SELECT

Owner, CAST(YEAR(Quarter) AS char(4)) + 'Q' + CAST(DATENAME(QUARTER,...

I, too, got different totals; mine add up to 82, the number of sample rows of data.

SELECT

Owner, CAST(YEAR(Quarter) AS char(4)) + 'Q' + CAST(DATENAME(QUARTER, Quarter) AS...

Maybe this?!:

SELECT

t1.DOCUMENT_NO,

RTRIM(CAST(t1."ENVIRONMENT_CD" AS VARCHAR(5))) + '*' + RTRIM(CAST(t1."ORDER_NO" AS VARCHAR(25)))

+ CASE WHEN TEST_REPORTING_MATERIAL_SID__COUNT > 1 THEN...

The "ON" clause after the "FROM" is not valid. That condition should just be in the WHERE conditions, since it's a correlated condition.

I don't know about Netezza, but the...

Instead of the overhead of a self-join, try this for case #3:

WHERE

myField LIKE '_%' + @SearchParameter + '%' AND

CHARINDEX(@SearchParameter, myField) >...

A "heap" is a table without a clustered index. It may or may not have nonclustered indexes.

You should review heaps carefully. Typically it's far better in SQL Server...

Here's my suggested code for this trigger.

CREATE TRIGGER [dbo].[MAYTABLE_A_IUD_WD]

ON [dbo].[MYTABLE]

AFTER DELETE, INSERT, UPDATE

AS

SET NOCOUNT ON;

DECLARE @action char(6)

...

N/A.

Please try code below. I didn't have any data to test it first, of course.

SELECT

a.ValetNO AS PlanNo,

cross_apply_1.Status1,

...