Changing compatibility level from 2008 to 2016How to detect compatibility errors - SQL Server 2012 Identify...
In the Lost in Space intro why was Dr. Smith actor listed as a special guest star?
Is the percentage symbol a constant?
Why don't you get burned by the wood benches in a sauna?
Is it really OK to use "because of"?
What if I miss a connection and don't have money to book next flight?
What happened to Hermione’s clothing and other possessions after she wiped her parents’ memories of her?
Is Screenshot Time-tracking Common?
Was Opportunity's last message to Earth "My battery is low and it's getting dark"?
What is an efficient way to digitize a family photo collection?
How to wrap a figure in exam document?
Coworker is trying to get me to sign his petition to run for office. How to decline politely?
Probability X1 ≥ X2
Expression for "unconsciously using words (or accents) used by a person you often talk with or listen to"?
Using Ansible, how can I take actions on each file in a specific location?
Disk space full during insert, what happens?
Is the UK legally prevented from having another referendum on Brexit?
How do I fight with Heavy Armor as a Wizard with Tenser's Transformation?
Coworker asking me to not bring cakes due to self control issue. What should I do?
How do I avoid the "chosen hero" feeling?
What can I do to encourage my players to use their consumables?
Crack the bank account's password!
How can I handle players killing my NPC outside of combat?
How to write Muḥammad ibn Mūsā al-Khwārizmī?
Is practicing on a digital piano harmful to an experienced piano player?
Changing compatibility level from 2008 to 2016
How to detect compatibility errors - SQL Server 2012 Identify NON-ANSI joins in SQL Server 2008 R2 on a Database that's in 2000 (80) compatibility modeDo I need to rebuild indexes when upgrading a DB from 2008 to 2012?SQL Server Upgrade 2008 -> 2016 / 100 to 130 compatibility slow queries, new CE killing meSQL Server 2016 Compatibility Level and Datetime 2Behavior Differences Running SQL 2017 in 130 Compat Mode vs. Running SQL 2016 in 130 Compat Mode?Moving to version 2016 from 2008 and Breaking Change Alert from Upgrade AdvisorBacking up a SQL 2008 DB, then restoring, gives a SQL 2005 (compatibility level 90) DBUpgrading SQL Server 2005 to 2016Will a SQL Server 2008 R2 MDF file work on SQL Server 2016 with Windows Server 2016?
I have a database with hundreds of stored procedure, views, triggers, function, ...
The database Compatibility Level is 2008 (100) and we would like to move it to 2016 (130).
The SQL Server version is 2016. We read that migrating the Compatibility Level could/would improve performance.
What is the best way to verify each object of the database to ensure working compatibility of the database? I already checked the "Upgrade Advisor" and it doesn't support the version of the database.
sql-server sql-server-2016 upgrade compatibility-level
add a comment |
I have a database with hundreds of stored procedure, views, triggers, function, ...
The database Compatibility Level is 2008 (100) and we would like to move it to 2016 (130).
The SQL Server version is 2016. We read that migrating the Compatibility Level could/would improve performance.
What is the best way to verify each object of the database to ensure working compatibility of the database? I already checked the "Upgrade Advisor" and it doesn't support the version of the database.
sql-server sql-server-2016 upgrade compatibility-level
add a comment |
I have a database with hundreds of stored procedure, views, triggers, function, ...
The database Compatibility Level is 2008 (100) and we would like to move it to 2016 (130).
The SQL Server version is 2016. We read that migrating the Compatibility Level could/would improve performance.
What is the best way to verify each object of the database to ensure working compatibility of the database? I already checked the "Upgrade Advisor" and it doesn't support the version of the database.
sql-server sql-server-2016 upgrade compatibility-level
I have a database with hundreds of stored procedure, views, triggers, function, ...
The database Compatibility Level is 2008 (100) and we would like to move it to 2016 (130).
The SQL Server version is 2016. We read that migrating the Compatibility Level could/would improve performance.
What is the best way to verify each object of the database to ensure working compatibility of the database? I already checked the "Upgrade Advisor" and it doesn't support the version of the database.
sql-server sql-server-2016 upgrade compatibility-level
sql-server sql-server-2016 upgrade compatibility-level
edited 12 mins ago
Paul White♦
52.2k14279452
52.2k14279452
asked 2 days ago
Lenny32Lenny32
1184
1184
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
For this number of jumps in compatibility level (or if you are being appropriately paranoid with a production application, for any jumps in compatibility level) a full application regression test is the only way to be absolutely sure.
Even if you have ensured that all the matters listed in the release notes either don't affect you or have been mitigated, you might find instances where code is relying on officially undefined behaviour which has changed (changes like this may not appear in release notes). For instance, when moving some of our work from 2005 to 2008r2 we experienced problems with a change in how some (admitedly odd) queries using FOR XML
generated their output.
Is there a tool that could help me for the migration (at least the obsolete types, function, ...).
– Lenny32
2 days ago
@Lenny32 - Probably not all the way from 2008 to 2016. If the DB were still on an older DB instance you could perhaps use the upgrade advisers in a stepwise fashion, upgrading one or two versions at a time.
– David Spillett
2 days ago
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%2f230378%2fchanging-compatibility-level-from-2008-to-2016%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
For this number of jumps in compatibility level (or if you are being appropriately paranoid with a production application, for any jumps in compatibility level) a full application regression test is the only way to be absolutely sure.
Even if you have ensured that all the matters listed in the release notes either don't affect you or have been mitigated, you might find instances where code is relying on officially undefined behaviour which has changed (changes like this may not appear in release notes). For instance, when moving some of our work from 2005 to 2008r2 we experienced problems with a change in how some (admitedly odd) queries using FOR XML
generated their output.
Is there a tool that could help me for the migration (at least the obsolete types, function, ...).
– Lenny32
2 days ago
@Lenny32 - Probably not all the way from 2008 to 2016. If the DB were still on an older DB instance you could perhaps use the upgrade advisers in a stepwise fashion, upgrading one or two versions at a time.
– David Spillett
2 days ago
add a comment |
For this number of jumps in compatibility level (or if you are being appropriately paranoid with a production application, for any jumps in compatibility level) a full application regression test is the only way to be absolutely sure.
Even if you have ensured that all the matters listed in the release notes either don't affect you or have been mitigated, you might find instances where code is relying on officially undefined behaviour which has changed (changes like this may not appear in release notes). For instance, when moving some of our work from 2005 to 2008r2 we experienced problems with a change in how some (admitedly odd) queries using FOR XML
generated their output.
Is there a tool that could help me for the migration (at least the obsolete types, function, ...).
– Lenny32
2 days ago
@Lenny32 - Probably not all the way from 2008 to 2016. If the DB were still on an older DB instance you could perhaps use the upgrade advisers in a stepwise fashion, upgrading one or two versions at a time.
– David Spillett
2 days ago
add a comment |
For this number of jumps in compatibility level (or if you are being appropriately paranoid with a production application, for any jumps in compatibility level) a full application regression test is the only way to be absolutely sure.
Even if you have ensured that all the matters listed in the release notes either don't affect you or have been mitigated, you might find instances where code is relying on officially undefined behaviour which has changed (changes like this may not appear in release notes). For instance, when moving some of our work from 2005 to 2008r2 we experienced problems with a change in how some (admitedly odd) queries using FOR XML
generated their output.
For this number of jumps in compatibility level (or if you are being appropriately paranoid with a production application, for any jumps in compatibility level) a full application regression test is the only way to be absolutely sure.
Even if you have ensured that all the matters listed in the release notes either don't affect you or have been mitigated, you might find instances where code is relying on officially undefined behaviour which has changed (changes like this may not appear in release notes). For instance, when moving some of our work from 2005 to 2008r2 we experienced problems with a change in how some (admitedly odd) queries using FOR XML
generated their output.
answered 2 days ago
David SpillettDavid Spillett
22.6k23267
22.6k23267
Is there a tool that could help me for the migration (at least the obsolete types, function, ...).
– Lenny32
2 days ago
@Lenny32 - Probably not all the way from 2008 to 2016. If the DB were still on an older DB instance you could perhaps use the upgrade advisers in a stepwise fashion, upgrading one or two versions at a time.
– David Spillett
2 days ago
add a comment |
Is there a tool that could help me for the migration (at least the obsolete types, function, ...).
– Lenny32
2 days ago
@Lenny32 - Probably not all the way from 2008 to 2016. If the DB were still on an older DB instance you could perhaps use the upgrade advisers in a stepwise fashion, upgrading one or two versions at a time.
– David Spillett
2 days ago
Is there a tool that could help me for the migration (at least the obsolete types, function, ...).
– Lenny32
2 days ago
Is there a tool that could help me for the migration (at least the obsolete types, function, ...).
– Lenny32
2 days ago
@Lenny32 - Probably not all the way from 2008 to 2016. If the DB were still on an older DB instance you could perhaps use the upgrade advisers in a stepwise fashion, upgrading one or two versions at a time.
– David Spillett
2 days ago
@Lenny32 - Probably not all the way from 2008 to 2016. If the DB were still on an older DB instance you could perhaps use the upgrade advisers in a stepwise fashion, upgrading one or two versions at a time.
– David Spillett
2 days ago
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%2f230378%2fchanging-compatibility-level-from-2008-to-2016%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