gh and obviously the time consumption on making query on those tables will b
e really high, so is there any way by which I can partition the table, I mea
n the records entered befor
e a particular date will go into some separate partition and will be archive
d on requirement the query can be passed to that partition.
Hope this could be the way to handle the large tables. Or if you can suggest
some ways or links to handle very large database then I'll be thankful for
you.
Thanks in advance
Regards,
SunilHi Sunil.
You can use partitioned views to do this. These can either be local or
distributed accross physical servers.
Do these tables have identities? If so, this is a gotcha but I have a work
around if you do.
Regards,
Greg Linwood
SQL Server MVP
"Sunil" <anonymous@.discussions.microsoft.com> wrote in message
news:4BC00EDE-6F44-4B1C-ACB0-F77D2035DE53@.microsoft.com...
quote:
> I have some tables in the large production database which suppose to grow
high and obviously the time consumption on making query on those tables will
be really high, so is there any way by which I can partition the table, I
mean the records entered before a particular date will go into some separate
partition and will be archived on requirement the query can be passed to
that partition.
quote:
>
> Hope this could be the way to handle the large tables. Or if you can
suggest some ways or links to handle very large database then I'll be
thankful for you.
quote:|||Design the table again for the larger table, I think the problem is caused
>
> Thanks in advance
> Regards,
> Sunil
by the design of table|||Partition the tables and use partitioned views to consolidate... You should
do lots of load testing to make sure this scales to suit your needs...
Wayne Snyder MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
(Please respond only to the newsgroups.)
I support the Professional Association for SQL Server
(www.sqlpass.org)
"Sunil" <anonymous@.discussions.microsoft.com> wrote in message
news:4BC00EDE-6F44-4B1C-ACB0-F77D2035DE53@.microsoft.com...
quote:
> I have some tables in the large production database which suppose to grow
high and obviously the time consumption on making query on those tables will
be really high, so is there any way by which I can partition the table, I
mean the records entered before a particular date will go into some separate
partition and will be archived on requirement the query can be passed to
that partition.
quote:
>
> Hope this could be the way to handle the large tables. Or if you can
suggest some ways or links to handle very large database then I'll be
thankful for you.
quote:
>
> Thanks in advance
> Regards,
> Sunil
No comments:
Post a Comment