Trace Flag impact to Mirrored Databases
up vote
1
down vote
favorite
I want to enable dead lock trace flag -t1222
on a production SQL Server 2014 instance. Many databases on this instance are configured with database mirroring. What (if any) impact to mirrored databases will occur after applying -t1222
and restarting the server?
sql-server sql-server-2014 mirroring trace-flags
add a comment |
up vote
1
down vote
favorite
I want to enable dead lock trace flag -t1222
on a production SQL Server 2014 instance. Many databases on this instance are configured with database mirroring. What (if any) impact to mirrored databases will occur after applying -t1222
and restarting the server?
sql-server sql-server-2014 mirroring trace-flags
3
Why not use extended events to track the deadlocks instead?
– vonPryz
5 hours ago
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I want to enable dead lock trace flag -t1222
on a production SQL Server 2014 instance. Many databases on this instance are configured with database mirroring. What (if any) impact to mirrored databases will occur after applying -t1222
and restarting the server?
sql-server sql-server-2014 mirroring trace-flags
I want to enable dead lock trace flag -t1222
on a production SQL Server 2014 instance. Many databases on this instance are configured with database mirroring. What (if any) impact to mirrored databases will occur after applying -t1222
and restarting the server?
sql-server sql-server-2014 mirroring trace-flags
sql-server sql-server-2014 mirroring trace-flags
edited 5 hours ago
Tom V
13.8k74676
13.8k74676
asked 6 hours ago
Nasar Babu Chowdary
63
63
3
Why not use extended events to track the deadlocks instead?
– vonPryz
5 hours ago
add a comment |
3
Why not use extended events to track the deadlocks instead?
– vonPryz
5 hours ago
3
3
Why not use extended events to track the deadlocks instead?
– vonPryz
5 hours ago
Why not use extended events to track the deadlocks instead?
– vonPryz
5 hours ago
add a comment |
1 Answer
1
active
oldest
votes
up vote
4
down vote
What (if any) impact to mirrored databases will occur after applying -t1222 and restarting the server?
Since 1222 writes deadlock information to the log, the impact to mirroring itself will be nothing. Secondary effects should also be intangible in a normal environment. I'd only be worried if, for some reason, you have so many deadlocks that the Errorlog ends up filling your drive as this is fairly benign.
Also, by default, the extended events session does track deadlock information but it may not have all of the deadlock graph given the size of the deadlock graph.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
What (if any) impact to mirrored databases will occur after applying -t1222 and restarting the server?
Since 1222 writes deadlock information to the log, the impact to mirroring itself will be nothing. Secondary effects should also be intangible in a normal environment. I'd only be worried if, for some reason, you have so many deadlocks that the Errorlog ends up filling your drive as this is fairly benign.
Also, by default, the extended events session does track deadlock information but it may not have all of the deadlock graph given the size of the deadlock graph.
add a comment |
up vote
4
down vote
What (if any) impact to mirrored databases will occur after applying -t1222 and restarting the server?
Since 1222 writes deadlock information to the log, the impact to mirroring itself will be nothing. Secondary effects should also be intangible in a normal environment. I'd only be worried if, for some reason, you have so many deadlocks that the Errorlog ends up filling your drive as this is fairly benign.
Also, by default, the extended events session does track deadlock information but it may not have all of the deadlock graph given the size of the deadlock graph.
add a comment |
up vote
4
down vote
up vote
4
down vote
What (if any) impact to mirrored databases will occur after applying -t1222 and restarting the server?
Since 1222 writes deadlock information to the log, the impact to mirroring itself will be nothing. Secondary effects should also be intangible in a normal environment. I'd only be worried if, for some reason, you have so many deadlocks that the Errorlog ends up filling your drive as this is fairly benign.
Also, by default, the extended events session does track deadlock information but it may not have all of the deadlock graph given the size of the deadlock graph.
What (if any) impact to mirrored databases will occur after applying -t1222 and restarting the server?
Since 1222 writes deadlock information to the log, the impact to mirroring itself will be nothing. Secondary effects should also be intangible in a normal environment. I'd only be worried if, for some reason, you have so many deadlocks that the Errorlog ends up filling your drive as this is fairly benign.
Also, by default, the extended events session does track deadlock information but it may not have all of the deadlock graph given the size of the deadlock graph.
answered 2 hours ago
Sean Gallardy
15k22347
15k22347
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f224725%2ftrace-flag-impact-to-mirrored-databases%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
3
Why not use extended events to track the deadlocks instead?
– vonPryz
5 hours ago