try this

declare

@value int

set

@value = 0

update

yourtable

set

@value = @value

as a general rule of thumb where possible always use foriegn key constraint to enfore referential integrity instead of triggers.

yes triggers can maintain denormailised figure and ensure fk constraint accross dbs but this is not the place to use them .

" use triggers to enhance referential integrity more so...

why would you want to break the referential integrity of the db introduce triggers that have to be maintained and ensure that the domain of you foreign keys are exclusive...

Dont htink so

upgrade to sql2005

What you going to do if the key values overlap? You wont know which table its really pointing at if there is a matching record in both. 

umm i reckon you would...

sql2000 does replicate schema changes you must reinitialise the subscriptions.

Forgot the interval bit

declare

@i int, @interval int

set

@i = 0, @interval

set @i = 0

update  RandomPermTable

ah yes didnt spot that was using different DDL code

Thanks Adam Unfortunatly this wont solve the problem.

The strange thing is that- i create two cubes with same data source using the same fact table and the same dimension in...

umm have you actually run the code. NOt sure why your getting nulls.

Rather than assuming id and extra column i am would insert the records in a tables variable which...

Heres a solution that doesnt use a loop (cursor) and should therefore by more efficient.

------------DDL----------------

-- prepare test data

declare

@table table