We help IT Professionals succeed at work.

What are the pros and cons of splitting one table out of a database due to it's size

204 Views
Last Modified: 2014-05-14
We are redesigning an MS SQL database. It's total size is approx 3.5GB and is not likely to grow much bigger than this.

One of the tables, the "Copy" table, contains a column with the datatype of "text" and this table is approx 1.5GB.

The database may be replicated between two servers.

The MS SQL version we will be launching with is 2012.

We are trying to determine whether we should split this one table out into a separate database or to leave it within the single database.

We're using hosted virtual servers with significant processing power.

Would it be recommended to split this Copy table out into a separate database for performance reasons or is that overkill for a database of this size?
Comment
Watch Question

This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Appreciate the quick response cheers4beers. I'll have my developers absorb the information in the links you've provided.
Senior DBA
CERTIFIED EXPERT
Most Valuable Expert 2018
Distinguished Expert 2019
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Thanks for the additional response Scott.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.