sql server 2005 - What are your thoughts on breaking up a large SQL table into several, based on a certain category id? -

We have a large desk that serves many different stored procedures on many websites, but generally Only related to the data in the table

= "Text">

If that means that If you are installing multiple databases on multiple servers, this is one of the recommended methods on the scale. If you mean multiple tables (same database or not) on the same server, then your profit will be less if any; And your administrative overhead will probably increase to keep them in a timeline and if there is any case on all the questions that kills several tables, then it will be less efficient.

The effect is not likely to be good or sick, what would you expect to be the benefit? (It is a typical rdbms antipattern for premature adaptation.)