All geek questions in one place

Are there any implications for creating cross-database calls in SQL 2005?

Are there any performance implications for database cross-calls in SQL 2005? In other words, is it better for performance to have a stored procedure and function executed in the same database where and where the data is?

+3
source share
4 answers

If the databases are on the same server instance, this is not so much. If they are in different server instances, you have the cost of transmitting requests and data. Therefore, I think the answer is yes, it is better for the performance to work in the same database.

+3
source

, . , , DR , . , , , . , - , , , - .

-, , . / , . , , .

+3

, , db, .

  • ( )
  • db
  • . . maitianed
  • BCP ( , ..)

( ), .

, ?

+1
source

GBN

The database that contains the data belongs to the third-party application MS Enterprise Server. We did not want to host our own SQL in this database. We decided to create a custom database that cross-queries if necessary.

0
source

Source: https://habr.com/ru/post/1703703/

More articles:


All Articles