Glad you made it work.

Snapshot agents tend to be CPU intensive.

Probably the load from All other jobs was affecting the entire process.

Anyway. Thanks for posting back

Michael (6/11/2008)

---

When executing query:

exec sp_MSforeachtable

@command1 = 'DELETE FROM',

@whereand = '(TSTAMP < '2007-01-01 00:00:00')'

I receive this error message:

Server: Msg 170, Level 15, State 1, Line 3

Line 3: Incorrect syntax...

mary_mormann (6/11/2008)

---

I have records which contains id,name,MoveNumber which looks like below.

1, Fred, 10

2, Wilma, 10-1

3, Barney, 101-1

4, Pebbles, 10-2

5, Marsha, 10-7

6, Tom, 97

7, Bob, 97-3

If I order by MoveNumber, it...

You are on the right track. Just make sure that your final query is covered by the appropriate indexes and you will finish *much* faster than the "java-cursor" I believe...

Sample Query, Data and DDL are required to answer your question.

If there are many trivial queries and those are the dominant in the server there are cases in which 2000 is faster than 2005. There have been many patches released...

KATHLEEN Y ZHANG (6/10/2008)

---

Thanks Noel.

I just tried to re-snapshot a publication and got the same message on snapshot agent 'waiting response from the server', then I checked the sysprocesses table...

you should verify the credentials for the Queue reader Agent Job

The response that is wating is probably the one on the "replica". You should check for contention on both distribution and subscription database.

IF the method you use to create the...

ahutch (6/6/2008)

---

Erm...I hit F7 and nothing happens. Oh well...

I think I know what you are referring to, but not sure how this is any easier than using the generate...

Well if you are a subscriber database then you don't have a choice.

But if you are not replicating or you are a publisher you can get rid of it 😉

Duration has only meaning in "Completed" events not in "starting" events.

Are you seeing those in "RPC /Batch Completed" ?

Ahhhh....

You have set NOT FOR REPLICATION. With that setting ON SQL Server considers the constraint as UNTRUSTED.

This is one of those "premature" optimization tips that wander around and that actually makes very little difference except on very (and I mean very) specific cases.