in other words :

INSERT INTO TABLE(x1,,...) VALUES (@x1,@x2,...)

WHERE TABLE.PRIMARY_KEY <> @YOUR_PRIMARY_KEY

Edited by - noeld on 12/16/2003 06:57:22 AM

I agree with the others, it is better to keep the code in separated triggers but just for the fun of it this is how you can do it:

IF SELECT...

You can try MS version also

I have some bad news for you,

YES YOU ARE RIGHT !!!

COLUMN_DEF IS HARDCODED AS convert(nvarchar(4000),NULL)

the reason: AFAIK that Default is NOT stored on any table as of SP3...

quote:

---

quote:

---

CREATE TABLE TBL (GRP INT, VALUE INT)

GO



INSERT TBL VALUES (1,...

1. set a job that runs the package

2. make sure to disable the job so that it does not run on a schedule

3.Then run: exec sp_start_job

quote:

---

Basically they are pulling them off the market. Microsoft is supporting them, just not selling them.

That's their perogative. With Yukon on...

declare @mytablename varchar(50)

set @mytablename = 'T'

Exec ('DROP TABLE ' + @mytablename)

CREATE TABLE TBL (GRP INT, VALUE INT)

GO



INSERT TBL VALUES (1, 1)

INSERT TBL VALUES (1, 2)

INSERT TBL VALUES (1, 3)

INSERT TBL VALUES (1, 4)

INSERT TBL VALUES (1,...

Can you insert the running total value at INSERT time?

But if you update the ClosingDate Values

an INDEXED VIEW with the previous query may do the Trick

as allways ......

is that a TEXT type or a varchar type?

I would calculate the Value at INSERT time so that you don't have to do it after the fact!!

quote:

---

Hi Stuart (stubob),

I agree with you. Pre-calculation makes sense. This calculation is done only once and it is a time-saver. (If you...

Is this what you are after ?

CREATE TABLE TDATA(DATEONDATA DATETIME, ITEM VARCHAR(10), CLOSINGPRICE MONEY, MOVINGVALUE MONEY)

INSERT TDATA VALUES('1-JAN-01','SUGAR',400,400)

INSERT TDATA VALUES('1-JAN-01','SALT',450,450)

INSERT TDATA VALUES('1-JAN-01','COFFEE',700,700)

INSERT TDATA VALUES('2-JAN-01','SUGAR',425,405)

INSERT TDATA...

I am 100% with Phill here you didn't specify if you need the count before or after and I believe for after Phill's a very good choice

...