And I'd also go with the one trigger route...

Which one is failing?

What do you get when you run this?

Select name, OBJECTPROPERTY(id, 'ExecIsTriggerDisabled') as TriggerIsDisabled from dbo.SysObjects where XType = 'TR' AND 1 = OBJECTPROPERTY(id, 'ExecIsTriggerDisabled')

Can you post the code of the failing/succeeding triggers?

It's all a matter of required precision >>

SELECT datediff(MONTH, convert(datetime, '2004-12-31', 120), convert(datetime, '2005-01-01', 120)) / 12.0 as W_Months, datediff(MINUTE, convert(datetime, '2004-12-31', 120), convert(datetime, '2005-01-01', 120)) / (60.0 * 24*365.256)...

HTH.

Hmm, I think you should look into replication for this )obviously not the only way, but that's the way I'd look into as it's all automatic).

You can find the quota info on the hd itself using windows explorer. That tells windows to keep X % or X MB of free space on the drive....

How do you intend to keep the table syncronized over time??

you can always count the number of minutes bewteen the dates and divide by (60*24*365.256)

1 - Is sql server started (can you access any of the tables, views)??

2 - Open enterprise manager, right click on the server (assuming it's stared), properties / security /

What...

Is the server service started?

What is the autenthication mode?

Are you sure you have the correct login/password for that database?

Do they contain the same data?

Can I see some sample data of matching rows and the ddl?

Do you have quotas in place??

Make sure you can't work there before jumping ship...

Believe me those procs are usefull to have .