|
|
Posted by Erland Sommarskog on 04/16/06 14:05
Peter (someone@someplace.com) writes:
> My question is: Can I say the derived table is instable in SQL server and
> causes the problem of the wrong result set here?
No, that would be to jump to conclusion. The cause for the problem is
likely to be much more specific. But since you did not include the actual
code, nor the underlying tables, there is not information enough to
recreate the problem. (And most likely tables and queries would not be
sufficient, as the data volumes may be required to get the incorrect
query plan that you apparently get.)
If you get this problem with SQL 2005, I suggest that you try extract
the tables to a database of its own, and ensure that the problem appears
there. Then submit a bug on http://lab.msdn.microsoft.com/ProductFeedback/.
If the data is not sensitive, you could attach the database to the bug.
Else just say in the error report that the database is available on
request. Obviously, the bug report should include information about what is
wrong about the result set.
If you get this problem with SQL 2000, I don't think there much that can
be done about it, since there apparently is a workaround. But if you are
able to reproduce the problem with a minimal set of data, so that you could
compose a script that creates tables, populates them and creates the
procedure you can post it to the newsgroup if you like. If nothing else,
people here can investigate if the problem is in SQL 2005 as well.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|