Glad you resolved it.

No clue why you got it. Maybe a job ported over from SQL 2000 and with something messed up by that?

On the dialog box on jobs, that shows steps and status. The jobs data in the summary view doesn't update except when you click "Refresh". The pop-up one...

Like this:

create table DTest1...

That trigger looks like it should work, at least at first glance. Can you tell me what you're trying to resolve with it? Does it give you an...

The first thing to do, actually, is to get that cursor out of the trigger. It calls a proc, and I'm sure you can make that proc into a...

The most common reason nested views end up slow is because of returning unused rows and columns.

If, for example, you have a view for:

create view MyView1

as

select MyTable1.PersonID, FirstName, LastName, DateOfBirth,...

chileu17 (9/26/2008)

---

Jerry Hung (9/26/2008)

---

Wow, that is LONG

How much was the fragmentation %? I wonder if REBUILD (instead of REORGANIZE) would've been quicker

Was this tested in other environments to estimate the...

If you actually have enough rows in the table variable to justify an index (which means over 1000 if I remember correctly), then you're better off using a temp table...

Why all the multiplying in the calculation? Do you have multiples of the same error?

I'm used to seeing stuff like this turned into a flat query and then Sum()...

I haven't found the dependencies data in SQL Server to be very reliable. If someone change's an object's name, it messes all of that up.

Including that in the Where clause should at least reduce the amount of logging overhead from the update, since less rows will be logged. I generally include that kind...

It depends on the indexed view, the query against it, and the indexes on the base tables in it. Sometimes SQL Server will use the view because that's the...

Check the RPC settings on both machines.

In that one case, yes,...