Interesting article, though I would have appreciated a bit more information to see the while picture, most importantly the external fragmentation of indexes, but also the internal fragmentation. Information about...

Pseudocode:

declare @var datatype;

select @var = function(@param) -- for scalar

select @var = col from schema.function(@param) -- for table valued

For table valued functions, note that @var will contain the first value returned...

First of all, I don't think this article is comprehensive enough, and as pointed out, it does not explain when to use (or not use) sequences. I've seen test showing...

Seems like the only solution would be to create an additional layer, as a web service or a .NET CLR proc, unless someone has a bright idea.

Looks very much like homework, yes. So, what about give it at try yourself, and then post your attempt to solve it?

Are you sure you that these columns are compressed? I would rather guess that the data is encrypted. If so, you could ask the developers for the encryption key, but...

The issue here is not the round, but the money data type. According to BOL, the money data type is precise to four decimal places. Unfortunately, this is only true...

Interresting solution, I had not thought of that approach, and getting rid of the cast makes it slightly faster.

Good to help. Inline Table Valued functions are underestimated in my opinion. I try to write most (or all) table valued functions inline, and I tend to convert some scalar...

You could try to make it an inline table valued function, and use cross apply against this function, but I don't know whether it would help in this case.

CELKO (3/26/2012)

---

I hate XML inside SQL. I also hate CLRs and anything that is not pure SQL. Mixed code cannot be optimized, requires programmers that know all the assorted...

GilaMonster (3/26/2012)

---

Nothing wrong with a guid primary key. What causes performance problems is a Guid column used as the clustered index key. So if you're going to have Guid primary...

One possible solution:

declare

@dt datetime;

select @dt = cast(cast(getdate() as date) as datetime)+cast(datepart(hour,getdate()) as float)/24

select @dt

Replace the two occurences of getdate() with your column...

Personally, I find a cast more clean code, I have not done any performance testing though to see if it is performing any differently than dateadd/datediff:

declare

@dt...

Max key length for an index is 900 bytes, so a varchar(1200) should not be used as an index key. You could consider crating a hash of it, and use...