Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sql777
Constraint Violating Yak Guru
314 Posts |
 Posted - 2005-04-25 : 12:19:57
|
| Hi,I have a project that will create a potentially very large database, the structure is similiar to a forums table, the items are referenced either from their ID or a childID that all the threads for a post reference to.Does performance degrate when a specific Table gets too large, or database?I'm thinking I could break the tables down and spread them accorss more tables since my application will not be effected by this.example:products1 products2 products3 products4instead of products.this ofcourse is because i'm assuing the actuall performance degradation is due to a single large table.correct? |
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2005-04-25 : 14:08:04
|
| Define "Huge"Brett8-) |
 |
|
|
sql777
Constraint Violating Yak Guru
314 Posts |
Posted - 2005-04-25 : 20:35:46
|
| 1-2 million rows. |
|
|
|
Lumbago
Norsk Yak Master
3271 Posts |
Posted - 2005-04-26 : 07:24:41
|
| 1-2 million rows hardly qualifies as huge but depending on what you are doing and how you are doing it, it could give give you plenty of performance problems. I just separated a few of my tables into two new tables, one with current data and one with historica data and then created a union all-view between them for queries that need both current and historic data. The performance gain was quite significant and my old table held about 2 mill rows...Just my 2 cents worth I guess.--Lumbago"Real programmers don't document, if it was hard to write it should be hard to understand" |
|
|
|
|
|
|
huge tables, forum like structure