Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have SQL Server 2008 R2 database which is currently about 80Gb.

About 10Gb of this is down to one table, and I wondered if there would be a performance gain if I moved this table into it's own database, and created a referencing synonym so that existing queries and SPs remained functional.

This database is ripe for an overhaul anyway, so that may be the obvious answer but I wondered if the synonym idea would be a quick win.

share|improve this question

migrated from Dec 24 '11 at 1:53

This question came from our site for professional and enthusiast programmers.

You don't have to move it to it's own database. You may be able to get a performance improvement by simply moving it to it's own filegroup within the existing database. The filegroup could then contain one or more files that are on a separate disk(s) from the ones the rest of the database is on.

share|improve this answer

Unless the new database lives on a much faster disk, you're not going to see any performance improvement, and may see some degradation. Better to attack the problem through analysis of the queries, health of the database and server. There's no quick solution, except maybe throwing hardware at it, more RAM, more CPU's, faster disks.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.