영어에서 Principal database 을 사용하는 예와 한국어로 번역
{-}
-
Colloquial
-
Ecclesiastic
-
Ecclesiastic
-
Programming
-
Computer
Mirror database may slow somewhat from the principal database.
Updates made by clients to the principal database are applied on the other copy of the database, known as the mirror database. .
This copy is known as the principal database.
The old mirror is assigned the principal role, and the old principal database takes on the new role of mirror.
This request of good data pages is an automated process that is transparent to any users who are currently accessing the principal databases.
But the mirror database might lag somewhat behind the principal database, though typically the gap between the databases is small.
The mirror database must have the same name as the principal database.
When database mirroring is deployed in a production environment, the principal database is the production database. .
The mirror server switches to the role of principal, and it offers its database as the principal database.
Actually, however, the client has been redirectedto the failover partner, which is the current principal database, and the client is updating the new principal database.
The partner that owns the principal role is known as the principal server, and its copy of the database is the current principal database.
Database mirroring involves redoing every insert, update, and delete operation that occurs on the principal database onto the mirror database as quickly as possible.
The copy of the database that is typically fully synchronized with the principal database.
Mirror database contains the same data as the principal database.
This copy of the database is known as the principal database.
The mirror database might lag somewhat behind the principal database.
The mirror database must have the same name as the principal database.
The database mirroring session adopts the same state as the principal database.
In database mirroring, the partner whose database is currently the principal database.
To achieve synchronousoperation for a session, the mirror server must synchronize the mirror database with the principal database.
Mirroring involves applying the transactionlog from every insertion, update, or deletion made on the principal database onto the mirror database. .
When a role switch occurs, the mirror server takes over the principal role and brings its copy of the database online as the new principal database.
Cannot execute as the database principal because the principal"dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission.