Database Replication/Mirroring for Reporting Purposes
I am pretty green to the administration end of databases, but I was hoping you guys could direct me on the right path.
I have Server 1, 2, and 3. They both identical versions of SQL Server, with an application. Within each instance of MS SQL Server, I have roughly 10 databases in each server. My goal is to replicate/mirror the data to a Server 4 so that reporting and alerts can be run off of the 'live' data without effective performance of the application running on Servers 1,2,3.
To be honest, I don't even know where to start:
Is this at all possible?
Is this a common practice?
Is there any type of recommended reading material?
sql-server replication mirroring
asked Jul 20 '16 at 18:05
etm124etm124
1013
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am pretty green to the administration end of databases, but I was hoping you guys could direct me on the right path.
I have Server 1, 2, and 3. They both identical versions of SQL Server, with an application. Within each instance of MS SQL Server, I have roughly 10 databases in each server. My goal is to replicate/mirror the data to a Server 4 so that reporting and alerts can be run off of the 'live' data without effective performance of the application running on Servers 1,2,3.
To be honest, I don't even know where to start:
Is this at all possible?
Is this a common practice?
Is there any type of recommended reading material?
sql-server replication mirroring
asked Jul 20 '16 at 18:05
etm124etm124
1013
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am pretty green to the administration end of databases, but I was hoping you guys could direct me on the right path.
I have Server 1, 2, and 3. They both identical versions of SQL Server, with an application. Within each instance of MS SQL Server, I have roughly 10 databases in each server. My goal is to replicate/mirror the data to a Server 4 so that reporting and alerts can be run off of the 'live' data without effective performance of the application running on Servers 1,2,3.
To be honest, I don't even know where to start:
Is this at all possible?
Is this a common practice?
Is there any type of recommended reading material?
sql-server replication mirroring
asked Jul 20 '16 at 18:05
etm124etm124
1013
I am pretty green to the administration end of databases, but I was hoping you guys could direct me on the right path.
I have Server 1, 2, and 3. They both identical versions of SQL Server, with an application. Within each instance of MS SQL Server, I have roughly 10 databases in each server. My goal is to replicate/mirror the data to a Server 4 so that reporting and alerts can be run off of the 'live' data without effective performance of the application running on Servers 1,2,3.
To be honest, I don't even know where to start:
Is this at all possible?
Is this a common practice?
Is there any type of recommended reading material?
sql-server replication mirroring
sql-server replication mirroring
asked Jul 20 '16 at 18:05
etm124etm124
1013
asked Jul 20 '16 at 18:05
etm124etm124
1013
asked Jul 20 '16 at 18:05
etm124etm124
1013
asked Jul 20 '16 at 18:05
etm124etm124
1013
asked Jul 20 '16 at 18:05
etm124etm124
1013
1013
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
What you are looking for is called Transactional Replication, which is very commonly used and a good solution for avoiding contention on a transactional database. There are three databases in a transactional replication system, which are the publisher, the distributor and the subscriber. The publisher is the source database, the distributor is where all changes to the publisher are sent for distribution to one or more subscribers. The distribution database can be on the same server as the publisher or a different server. When you create a publication, you choose the articles to be included, such as tables, views, procedures, etc, and whenever a change is made to any of the objects and gets recorded in the transaction log, an agent, which is an executable, reads the transaction log, packages the change and sends it to the distribution database. Then a separate agent, or executable, takes the packages from the distribution database and applies them to the subscriber.
You will be setting up a publication and subscriber on servers 1,2 and 3 and have all subscriptions point to a database on server 4. There are several articles on MSDN that have good descriptions of transactional replication.
answered Jul 20 '16 at 18:43
Michael KeleherMichael Keleher
659310
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f144470%2fdatabase-replication-mirroring-for-reporting-purposes%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
What you are looking for is called Transactional Replication, which is very commonly used and a good solution for avoiding contention on a transactional database. There are three databases in a transactional replication system, which are the publisher, the distributor and the subscriber. The publisher is the source database, the distributor is where all changes to the publisher are sent for distribution to one or more subscribers. The distribution database can be on the same server as the publisher or a different server. When you create a publication, you choose the articles to be included, such as tables, views, procedures, etc, and whenever a change is made to any of the objects and gets recorded in the transaction log, an agent, which is an executable, reads the transaction log, packages the change and sends it to the distribution database. Then a separate agent, or executable, takes the packages from the distribution database and applies them to the subscriber.
You will be setting up a publication and subscriber on servers 1,2 and 3 and have all subscriptions point to a database on server 4. There are several articles on MSDN that have good descriptions of transactional replication.
answered Jul 20 '16 at 18:43
Michael KeleherMichael Keleher
659310
add a comment |
What you are looking for is called Transactional Replication, which is very commonly used and a good solution for avoiding contention on a transactional database. There are three databases in a transactional replication system, which are the publisher, the distributor and the subscriber. The publisher is the source database, the distributor is where all changes to the publisher are sent for distribution to one or more subscribers. The distribution database can be on the same server as the publisher or a different server. When you create a publication, you choose the articles to be included, such as tables, views, procedures, etc, and whenever a change is made to any of the objects and gets recorded in the transaction log, an agent, which is an executable, reads the transaction log, packages the change and sends it to the distribution database. Then a separate agent, or executable, takes the packages from the distribution database and applies them to the subscriber.
You will be setting up a publication and subscriber on servers 1,2 and 3 and have all subscriptions point to a database on server 4. There are several articles on MSDN that have good descriptions of transactional replication.
answered Jul 20 '16 at 18:43
Michael KeleherMichael Keleher
659310
add a comment |
What you are looking for is called Transactional Replication, which is very commonly used and a good solution for avoiding contention on a transactional database. There are three databases in a transactional replication system, which are the publisher, the distributor and the subscriber. The publisher is the source database, the distributor is where all changes to the publisher are sent for distribution to one or more subscribers. The distribution database can be on the same server as the publisher or a different server. When you create a publication, you choose the articles to be included, such as tables, views, procedures, etc, and whenever a change is made to any of the objects and gets recorded in the transaction log, an agent, which is an executable, reads the transaction log, packages the change and sends it to the distribution database. Then a separate agent, or executable, takes the packages from the distribution database and applies them to the subscriber.
You will be setting up a publication and subscriber on servers 1,2 and 3 and have all subscriptions point to a database on server 4. There are several articles on MSDN that have good descriptions of transactional replication.
answered Jul 20 '16 at 18:43
Michael KeleherMichael Keleher
659310
What you are looking for is called Transactional Replication, which is very commonly used and a good solution for avoiding contention on a transactional database. There are three databases in a transactional replication system, which are the publisher, the distributor and the subscriber. The publisher is the source database, the distributor is where all changes to the publisher are sent for distribution to one or more subscribers. The distribution database can be on the same server as the publisher or a different server. When you create a publication, you choose the articles to be included, such as tables, views, procedures, etc, and whenever a change is made to any of the objects and gets recorded in the transaction log, an agent, which is an executable, reads the transaction log, packages the change and sends it to the distribution database. Then a separate agent, or executable, takes the packages from the distribution database and applies them to the subscriber.
You will be setting up a publication and subscriber on servers 1,2 and 3 and have all subscriptions point to a database on server 4. There are several articles on MSDN that have good descriptions of transactional replication.
answered Jul 20 '16 at 18:43
Michael KeleherMichael Keleher
659310
answered Jul 20 '16 at 18:43
Michael KeleherMichael Keleher
659310
answered Jul 20 '16 at 18:43
Michael KeleherMichael Keleher
659310
answered Jul 20 '16 at 18:43
Michael KeleherMichael Keleher
659310
659310
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f144470%2fdatabase-replication-mirroring-for-reporting-purposes%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
