Re: Querying a MS SQL View...
- From: "Jean Dupond" <jdupond@xxxxxxxxxx>
- Date: Fri, 21 Dec 2007 10:21:57 -0800
Thank you for taking the time to answer my question(s).
Our manager decided to split the tables because a lot of its data was
getting "old." The table that was split was the table containing a record
of sales record for the last five years. Since the data getting less
relevant as it ages, they decided to split it between a 'current' table
(with the last six month of data) and a 'history' table (with the rest of
the data).
"Del Murray" <Del.Murray@xxxxxxxxxxxxxx> wrote in message
news:476ac484@xxxxxxxxxxxxxxxxxxxxxxxxx
Vitali is right, splitting the tables now seem easy but later on you will
probably regret it.
You did not say why you split the tables. If it is a performance problem
then if you tell us what is happening we can probably suggest solutions
for that.
.
- Follow-Ups:
- Re: Querying a MS SQL View...
- From: Del Murray
- Re: Querying a MS SQL View...
- References:
- Querying a MS SQL View...
- From: Jean Dupond
- Re: Querying a MS SQL View...
- From: Vitali Kalinin
- Re: Querying a MS SQL View...
- From: Del Murray
- Querying a MS SQL View...
- Prev by Date: Re: Querying a MS SQL View...
- Next by Date: Re: Querying a MS SQL View...
- Previous by thread: Re: Querying a MS SQL View...
- Next by thread: Re: Querying a MS SQL View...
- Index(es):