DAT283

OUTPUT clause - knowing what goes in, and what you've accidentally taken out

Rob Farley — Sat, 04 Oct 2008 00:08:06 GMT

The OUTPUT clause has to be one of the best T-SQL features out there. It was new in SQL Server 2005,

re: DAT283

Rob Farley — Thu, 18 Sep 2008 03:54:17 GMT

Glad you enjoyed it. There's a link to the slides here:

msmvps.com/.../improving-your-t-sql-arsenal-slides.aspx

(these are user-group slides, without the TechEd branding)

Rob

re: DAT283

IT — Wed, 17 Sep 2008 23:37:11 GMT

Hi Rob

Just want to say thanks for the TechED AU DAT 283, It was one of the best time spent learning all the tips.

Great Job and Well done :-)

Cheers

OT: Improving my T-SQL What?

Thomas Williams Tech Blog — Mon, 15 Sep 2008 03:02:14 GMT

OT: Improving my T-SQL What?

re: DAT283

Rob Farley — Wed, 03 Sep 2008 02:49:23 GMT

Ah, true... I had originally been inserting 8000 rows, but then extended it to more. I should change it and make the '4' bigger.

It's a tip that I got from Ward Pond's similar presentation at TechEd US.

Thanks for the heads-up

Rob

re: DAT283

Thomas Williams — Wed, 03 Sep 2008 01:18:20 GMT

Hey Rob, I downloaded your scripts for a sqizz (thanks!), and found something in your "14-binarylike.sql" script where you cast a number as VARCHAR(4), which means that numbers after 9,999 appear as *: "...This is my *th long string, right?..."

Not sure if this is what you intended!

Good luck with your presentations :-)

Thomas