So what is the actual error message you are getting with the second proc?

😎

Looks to me that you have one too many "end" statements in the second stored proc.

😎

Better if you provide it as INSERT statements so that whoever decides to give it a go just has to cut, paste and execute. Some people don't have the...

The sooner you can provide the schema and some sample data the better. Suggestion for the schema and data, primary key(s) on the table, and the additional columns needed...

Jeff,

I'd be real interested in seeing that, and testing it as well. I have never seen that myself, so that has to be a Missouri moment (show me).

Thanks,

Lynn

Try this in a test environment:

DELETE PW -- COUNT(1)

FROM

performance_esx3_workload PW

INNER JOIN performance_sample PS

on (PW.sample_id...

Post your code you wrote.

😎

There are two issues here. The first is that the update is taking a long time, and second as a result the log file is filling up the disk...

That's what I forgot to put in that post on another thread, a BACKUP LOG!

Yes, you need to do that as well. As I asked earlier, if you post...

The BEGIN and END may not be necessary, but I find it makes it easier to see what code makes up a trigger, stored procedure etc. Especially true if...

Okay, I have to bite on this one. What server settings prevent you using indexed views?

😎

Sounds like you need to break down your update into smaller batches instead of one big update. Could you post your update query?

😎

This gets into basic BOOLEAN LOGIC. Your where clause is this:

That is equvilent to this:

For proof...

Read books and white papers is good, but you also need to get hands on experience as well. One thing you should also consider is purchasing SQL Server 2005...

Read BOL topics DDL Triggers and Event Notifications.

😎