You need the lock acquired event.

Do NOT do that on a production server, that's a high-volume event, it can have severe impact on the server if it's already under any...

No, they're not.

If you want to see the order, try a profiler trace or extended events (and don't do that on a production DB)

Please note: 5 year old thread.

Koen Verbeeck (8/5/2014)

---

GilaMonster (8/5/2014)

---

In that case, for 5+ years experience:

Name...

In that case, for 5+ years experience:

Name 3 backup types...

What do you mean? What kind of questions they'll ask in what context?

MikaS (8/5/2014)

---

What I wanted to say is that if someone takes a Full backup outside the regular backup schedule without using the COPY_ONLY, there's a possibility of ending up with...

That won't break the backup chain. Can make it hell to restore if...

To break the backup chain:

- Switch to simple recovery and back to full

- Delete a log backup file (the .trn)

- Delete the transaction log

- Revert to a snapshot

If the questions have worn you out, may I suggest a couple of maths limericks?

http://iwastesomuchtime.com/on/?i=93785

A dozen, a gross and a score

plus three time the square root of four

divided by seven

plus...

iasher (8/4/2014)

---

The table referenced in the FROM clause ("attorney") is actually the source table, but it's the target table (@IA_CourtCostReport) that's causing the problem, so I'm not sure how to...

iasher (8/4/2014)

---

Which FROM...

You need to alias table variables in the FROM, and use the aliases in the other clauses. You can't refer to @tbl.somecolumn anywhere, it's not considered valid

btw, are table variables...

No, not sp_updatestats (which does a sampled...

jcrawf02 (8/4/2014)

---

Jesus Grant, you throw this one to the OP like it's a "querying for dummies" book or something, and while I cannot disagree that reading it would give you...