Jeff Moden (6/26/2008)

---

And, that is precisely why I'd use float instead... but, whatever... it's really hard to convince people even with...

Having worked on a financial system in the early 90's where we were computing gain/loss per share per day it got quite interesting with the precision factor. In particular...

I can't take credit for the actual solution. I'm just re-providing something that...

I don't see why the data is split between the two tables. It would be easier if they were both in the same table. You would have only...

Also knowing Oracle, I do wish that there was a ROWID equivalent in SQL Server. I'm also aware that it is used in "finding duplicate" queries.

In SQL Server 2005...

Yes, as it has been done before SQL Server supported the hierarchical CTE (WITH) syntax.

If however, your looking for the equivalent of Oracle's robust CONNECT BY, you're out of luck....

I'm going to add my voice re: sp_describe_cursor_columns being a correct answer.

Granted, it will return a number of rows which can be counted up, but that number is the number...

I somewhat disagree that a TIMEOUT can be used to end a WAITFOR. It cannot be used independently and is only an optional modifier of the Service Broker message.

The "corrected" SP2 can also be labeled 3050 or 3054 depending upon what version was installed and then patched.

I installed the original SP2 and then applied the fix issued immediately...

I strongly suggest that you use CONTAINS vs. FREETEXT in order to have better control over the search syntax.

Several things (from experience).

1. Note that the CONTAINS function can utilize a variable. See the BOL. So you can build the search string in your application and then...

Matt Whitfield (5/30/2008)

---

And, basically, from a performance standpoint (which is where I was coming from in the first place), it will make as much difference as trying to stop a...

Again, a typical "off the cuff" remark without thinking. I'm not saying ALL the time. One thing that a...

Since this is SQL Server 2005, you should be using SQLCMD vs. OSQL. OSQL is obsolete.

The lock...