Link to home
Start Free TrialLog in
Avatar of PhilCarlyle
PhilCarlyle

asked on

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

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?
SOLUTION
Avatar of cheers4beers
cheers4beers
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of PhilCarlyle
PhilCarlyle

ASKER

Appreciate the quick response cheers4beers. I'll have my developers absorb the information in the links you've provided.
ASKER CERTIFIED SOLUTION
Avatar of Scott Pletcher
Scott Pletcher
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks for the additional response Scott.