SQL Server is one of the best products to come out of Microsoft, but not every professional knows how to use it effectively. For example, some might find it difficult to create a stored procedure but ...

I have a database that's got (amongst other things) two tables: one for astronomical objects (called tblObject) and another that holds measurements for those objects (called tblMeasurement).

We've got a strange problem here and I'm hoping someone has some kind of idea as to what could be causing it.<BR><BR>We've got a stored procedure in Sql Server 2005. It's not terribly complicated but ...