Is there any practical sense in separating SQL tables, procedures, etc. modules into separate databases? Will the load on the database, server decrease?

P

P

Programep2017-02-01 14:34:57

Transact SQL

Programep, 2017-02-01 14:34:57

Is there any practical sense in separating SQL tables, procedures, etc. modules into separate databases? Will the load on the database, server decrease?

Good afternoon!
Is there any practical sense in separating tables, procedures, etc. modules into separate databases? Will the load decrease?
Or does it make no sense, and is it even better to store everything in one big database?

Reply

Answer the question

Answer the question

In order to leave comments, you need to log in

1 answer(s)

R

res2001, 2017-02-01
@Programep

The load will increase.

Similar questions

I

Igor2014-06-26 11:58:02

How to properly store T-SQL code snippets? 2Reply

M

Max Trophy2016-08-10 22:08:29

How to upload data from a table to a txt file using t-SQL? 0Reply

E

ellz2019-02-13 22:56:58

Why does procedure contains an unresolved reference to an object occur? 1Reply

T

TemaKam2021-01-26 16:38:53

How to display a list of books that all library subscribers have read? 1Reply

M

Max Trophy2017-01-12 13:39:25

How to use cross join t-sql? 1Reply

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question