Maximum table size

Hello

My enterprise has SQL SERVER2008 with many databases and each with many tables.

What is the maximum disk size of a table in sql server before the BBDD lose performance?

This table only made Inserts and Updates. The records are updated only by primary key

Best Regards
JaimesastreAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

seethaaCommented:
There  is no limitation, it all  depends upon

1. Retention period
2. Number of records
3. Amount  of user targetted based  on it you may  go for partition.

Aslong  as your DB configured with good  hardware and parallel  option, the back-up will run fast...
0
Anthony PerkinsCommented:
What is the maximum disk size of a table in sql server before the BBDD lose performance?
It depends.
0
JaimesastreAuthor Commented:
Hello

I need the size aprox: 3GB, 6GB, 60GB .....

Thanks
0
jogosCommented:
It depends as in :

Insert
When you insert and have a clustered key that is not continuous then reorganizations must take place.
Must db expand regularly during an insert or is there always suffient allocated space.
How many indexes must be maintained

Update
Does it expand rowsize (page full?). Does it update columns that are in many indexes?
How does your update find the record/records to update (index or table scan? ). One update for many records at a time or many updates for one record at a time.

Never reads? How index seek or scan? Filtered indexes, table partitioning

Other considerations for that db
Transaction model (full, simple, bulk logged). Locking by other processes that slow down or your process locks other processes. Maintenance (free space, index fragmentation, frequency TLOG backup).

Instance/hardware
Memory , disk configuration, CPU's , tempdb and how your large table access fits in the load with other processes/databases/storage/network.
Ex. loading and reports at night ... but not in backup window


The list is open

A 30MB table can be more a daily problem as 3GB table ..... it depends
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Anthony PerkinsCommented:
Exactly! Size does not matter.  What counts is your hardware, how well designed are your tables and how well optimized are your queries.  They could be 3TB and be lightening fast or be 3MB and be a dog.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.