|
|
Posted by Erland Sommarskog on 10/01/62 11:21
Plaztik (plaztik8@yahoo.com) writes:
> We want to know the customer's ArriveDate and DepartDate (volatile,
> derived data), just because it is easier for humans to work with. This
> view that people may like to see cannot dictate how the system deals
> with transactional, historical, and accounting data under the covers,
> though. The example above is extremely common and even much simpler
> than others that occur daily. Things are the way they are for a
> reason.
>
> Hopefully that cleared some things up.
Thanks for taking your time to explain your business a little more,
although it's none of our business (pardon the pun). It's a great example
to show that there are a lot more in a system that from what you can see
in a query. For instance, the need to be able to cancel one day within
a reservation is one that may not be obvious to someone who only knows SQL
well, but have no experience of accounting or don't realise the relation
to accounting.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
Navigation:
[Reply to this message]
|