troubleshooting Question

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

Avatar of PhilCarlyle
PhilCarlyle asked on
Windows Server 2012Microsoft SQL Server
5 Comments3 Solutions206 ViewsLast Modified:
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?
Join our community to see this answer!
Unlock 3 Answers and 5 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 3 Answers and 5 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros