Do a forum search here. IIRC, this has been discussed here a few days ago. Otherwise, maybe http://www.sqldts.com has an answer.

Thanks for explanation. I'll keep it in mind for future reference.

...and I always thought this fora here are kind of SQL Server's own country.

See, if this helps:

http://www.iisfaq.com/admin/Portal/LinkClick.aspx?mid=2176&Link=3117

Q1: No, a cursor is _very_ seldomly the right way. But without your DDL, it's like a shot in the dark.

Q2: Look at the example given in BOL under DECLARE...

Wow, while I personally think, one shouldn't over-interpret each of Joe's words (or even take it personally) this was a nice explanation, Steve. Though I don't agree with having the...

Well, I would say, usually SQL Server is doing a good job at determine a good - optimal way to execute a statement. However, as has been said, a "hint"...

Michael,

have I missed something? Any news on this?

Joe,

on a sidenote. Have you ever tried to assign 23:59.59.99999 to a datetime?

declare @foolme datetime

set @foolme = '23:59.59.99999'

select @foolme

Server: Nachr.-Nr. 241, Schweregrad 16, Status 1, Zeile 2

Syntaxfehler beim Konvertieren...

Sounds good. Glad I could help.

See, if this helps:

http://www.microsoft.com/technet/itsolutions/migration/unix/sybsqlsv/default.mspx

http://www.microsoft.com/resources/documentation/sql/2000/all/reskit/en-us/part2/c0661.mspx

Any specific reasons for it?

Aah, doing this fixed income relative value thing. It's getting interesting when you need to implement swap spread models, volatility forecasting or skew models.

Good luck

You should be able to see each step SQL Server is making by examining the execution plans of both alternatives.

Jeff, I might miss something, but I don't the table AUX explicitely created in Julia's script.

Anyway, I get an error when I try to...

I guess the main reason for this is that it is by design. Actually I can't think of a valid reason for this behaviour other than Microsoft didn't implemented it...