No performance advantage.

No, you were talking about people being ignorant of things...

I don't...

Sounds like you've got a handle on it now. Cool biz.

I'm going to have to second the statement about UDFs. Inline query UDFs are fine, but multi-value and scalar are usually just a good way to kill server performance.

It's possible. It would be extraordinarily difficult to do without leaving traces, but it is possible.

There are better options for auditing. Take a look at these (shameless self-promotion, I know):

http://www.sqlservercentral.com/articles/Auditing/63247/

http://www.sqlservercentral.com/articles/Auditing/63248/

Just tested the speed. Scott's right.

Here's the test set-up:

USE [ProofOfConcept]

GO

/****** Object: Table [dbo].[UPR00900] Script Date: 08/07/2009 11:32:44 ******/

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

SET ANSI_PADDING OFF

GO

CREATE TABLE...

Cast to Int, do the math, recast back to varchar and add the leading zeroes back on.

declare @String varchar(10), @Number int;

--

select @String = '000009', @Number = 1;

--

select right('0000000000' + cast(cast(@String...

Chad Crawford (8/7/2009)

---

If you don't have a place for this...

talltop (8/7/2009)

---

I'll take your word for it Gail, but I must say with billions of dollars of corporations revenue on SQL Server databases nowadays this is truly a scary thing...

What's the definition for the primary key for the table? (Assuming there is one.)

The last two places I worked had unofficial policies that made it possible for me to take extra time off if I worked extra hours. Work the weekend, then...

Definitely odd.

Now I have to look at the copy of 2008 I have at home. You made me curious.

Personally, I find the Pivot and Unpivot syntax for SQL a bit cryptic. I also think the Pivot command is about as useless as a refrigerator in Antarctica. ...