Usually I capture procedure calls using trace events and then you know which procedures on which databases are running long or using more cpu.

With 2005 & 2008, you can also...

But not deletion when the keys are in use, right?

Today you just want to find out which procs are hitting. Tomorrow you're going to realize that you can begin to run aggregates and groupings to put out more meaningful...

Only if you're assuming that the entire set of lookup values is replaced each year. If the assumption is that the lookup value consists of the value and the year...

You'll probably need three inserts, but you can insert into each of the parent tables, get the ID's generated and then insert into the third table based on those ID's...

iqtedar (12/16/2008)

---

thanks again for being prompt...do u mean to say that i will need to filter the events so that i do not get the text data...and then transfer into...

Sure, you can use the OUTPUT clause of the INSERT query. This will allow you to capture ID's created during the INSERT and you can then pass them on to...

Tune the query is the first thing that comes to mind. Make sure you've got the right indexes in place on the tables and that the query is using them...

GilaMonster (12/16/2008)

---

Grant Fritchey (12/16/2008)

---

I actually said to one parent after giving their baton twirling, uh, I mean bo handling, son a low score, "You do know that this is meant...

You can load the file into a database and then run queries against it. That's how I've been doing it for years. That way you can get aggregates and see...

It is. I always forget to mention that part.

Lynn Pettis (12/16/2008)

---

Ian Massi (12/16/2008)

---

Interesting topic. I'd want to become a lumberjack. I'd sleep all night and I'd work all day... then again I do that now too....

Jeff Moden (12/16/2008)

---

Did that too. The most difficult stuff to judge is kata... it's like judging a dance competition... put all the flair and flash in that you want,...

OK. First off, don't collect StmtComplete events as part of a general data collection process. They are for targeted troubleshooting only. Second, I wouldn't worry overly much about the logout...

It's worth mentioning, since you're building a repeatable and well defined process around moving data out of the system, I'd suggest looking at partitioning the table. Partitioning would allow you...