Answer the question
In order to leave comments, you need to log in
Cut DB. How?
Good day to all
The problem is the following. There is a legacy product with a huge database (SQL Server). To work with the database itself, we use DB Project. The main dilemma is that db live spends a lot of time and periodically hangs on such volumes, but it is damn convenient in our development. Therefore, in order for it to work faster, it is necessary to reduce the size of the database. Whether there is any possibility to cut an available DB into any component parts: smaller bases\schemes\whatever? And if so, how?
Answer the question
In order to leave comments, you need to log in
Of course have.
1. You can divide one base into several, you will need to rewrite queries taking into account this division. This can be quite a lot of work, but the advantage can be that one of the databases can be moved to another physical server, connections on the servers can be set up, and requests will go through transparently for the client, as if the databases are on the same server.
2.You can create an additional file group in one database, configure its location on other physical disks than the main file group. Next, create database files in a new filegroup and transfer the necessary tables to these files. This method is less flexible than the first one, but it also allows some optimizations. In addition, this method does not cancel the first and vice versa.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question