[font="Verdana"]Might be worth having a look at Gail Shaw's excellent article on performance issues. She goes through how to use trace on the server.

Also, you can use the object_name(id)...

[font="Verdana"]I like my merlots, I admit. But I have been more keen on syrahs (shiraz for you aussies) of late.[/font]

Jeffrey Williams (6/17/2009)

---

GSquared (6/17/2009)

---

I used Cache about 5 years ago, for one project. My main issue with it was the nearly complete lack of tools for building and managing...

8kb (6/17/2009)

---

Management seems to want us to take the approach of Type 3 since our current requirement is only to show the last value previous to the update (not necessarily...

Paul White (6/17/2009)

---

I understand it is just a documentation oversight - but if we commit ourselves to never using 'undocumented' syntax (Barry!), how should we write an UPDATE from a...

RBarryYoung (6/16/2009)

---

I've always suspected that...

[font="Verdana"]The "type 2 slowly changing dimension" is a good approach for not needing a separate history or audit log table.

You don't actually have to use a dimensional model to use...

Digs (6/16/2009)

---

When i wish to rebuild ( or even truncate table, re insert into a new table, or whatever I wish to do) the table to remove the deleted '1'...

[font="Verdana"]The simple answer is: you can't work with multiple result sets returned from the same stored procedure (yes, I've tried it too.)

You can have a parameter to the stored procedure...

[font="Verdana"]I'm wondering whether it's more like this? (So it only filters where Col3...

[font="Verdana"]Or:

alter table tablename add constraint userkey unique (userid, datetime_entered);

I'm still struggling to see the value of the bigint...

[font="Verdana"]Whew!

In which case, a table variable being passed around would be fine.

[/font]

[font="Verdana"]Unless you are talking about the...

ken.trock (6/15/2009)

---

Thanks for looking at this. I'll take a look at table vars and error handling. These procs operate on anywhere from several hundred rows to a worst case scenario...

[font="Verdana"]Aside from issues in design for stored procedures that only accept one "row" of data...

I'd take a copy of what you need to process and put it in a temporary...