|
|
Posted by David Portas on 03/06/06 21:53
RickW wrote:
> Here's the thing I really don't get: If by definition (as always) and
> now in fact (with SS2005) you simply cannot return an ordered set from a
> view, how exactly are you supposed to cope with that in an application?
>
Use a proc. Or use ORDER BY in whatever other query accesses the view.
I could sympathise with a low budget, part-time developer who has to
deal with this but apparently you have little excuse. If your shop is
large enough to have a DBA and develops as much code as you seem to
imply then programming standards, best practices and peer reviews ought
to be in place to prevent screw ups. Your business has a right to
expect that from you. How about setting someone to document some better
programming standards?
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
Navigation:
[Reply to this message]
|