How do I configure my SQL Server instance to use a different Edition with minimal side effects?
I'm in the process of migrating an old server running Windows 2008 R2 with SQL 2012 Express to a new server running SQL Server 2017 Standard and Windows 2016. I would like to mirror databases between them, but the Express Edition doesn't support it. I tried to upgrade it to SQL 2012 Standard Evaluation, but I received the following error:
Failed The selected SQL Server instance does not
meet upgrade matrix requirements.
I discovered this isn't possible:
Upgrade SQL Server 2012 Express to Evaluation Edition
I was forced to install SQL Server 2012 Evaluation as a new side-by-side instance and named it ./SQLSERVER2. In order to use this instance, however, it would require moving a ton of data files and changing the instance names in all my configuration files. This will also require server downtime as well. This will be a major PITA without the humous and I want to avoid it if at all possible.
Is there a way of reconfiguring ./SQLSERVER to use the Standard Evaluation Edition with minimal downtime and side-effects?
sql-server upgrade mirroring instance
edited Oct 26 '18 at 5:55
Colin 't Hart
6,63682634
asked Oct 26 '18 at 4:31
ATL_DEVATL_DEV
1011
bumped to the homepage by Community♦ 13 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'm in the process of migrating an old server running Windows 2008 R2 with SQL 2012 Express to a new server running SQL Server 2017 Standard and Windows 2016. I would like to mirror databases between them, but the Express Edition doesn't support it. I tried to upgrade it to SQL 2012 Standard Evaluation, but I received the following error:
Failed The selected SQL Server instance does not
meet upgrade matrix requirements.
I discovered this isn't possible:
Upgrade SQL Server 2012 Express to Evaluation Edition
I was forced to install SQL Server 2012 Evaluation as a new side-by-side instance and named it ./SQLSERVER2. In order to use this instance, however, it would require moving a ton of data files and changing the instance names in all my configuration files. This will also require server downtime as well. This will be a major PITA without the humous and I want to avoid it if at all possible.
Is there a way of reconfiguring ./SQLSERVER to use the Standard Evaluation Edition with minimal downtime and side-effects?
sql-server upgrade mirroring instance
edited Oct 26 '18 at 5:55
Colin 't Hart
6,63682634
asked Oct 26 '18 at 4:31
ATL_DEVATL_DEV
1011
bumped to the homepage by Community♦ 13 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Install them side by side, then backup the database from Express Edition and restore it to Standard Edition.
– Randolph West
Oct 26 '18 at 21:31
add a comment |
I'm in the process of migrating an old server running Windows 2008 R2 with SQL 2012 Express to a new server running SQL Server 2017 Standard and Windows 2016. I would like to mirror databases between them, but the Express Edition doesn't support it. I tried to upgrade it to SQL 2012 Standard Evaluation, but I received the following error:
Failed The selected SQL Server instance does not
meet upgrade matrix requirements.
I discovered this isn't possible:
Upgrade SQL Server 2012 Express to Evaluation Edition
I was forced to install SQL Server 2012 Evaluation as a new side-by-side instance and named it ./SQLSERVER2. In order to use this instance, however, it would require moving a ton of data files and changing the instance names in all my configuration files. This will also require server downtime as well. This will be a major PITA without the humous and I want to avoid it if at all possible.
Is there a way of reconfiguring ./SQLSERVER to use the Standard Evaluation Edition with minimal downtime and side-effects?
sql-server upgrade mirroring instance
edited Oct 26 '18 at 5:55
Colin 't Hart
6,63682634
asked Oct 26 '18 at 4:31
ATL_DEVATL_DEV
1011
I'm in the process of migrating an old server running Windows 2008 R2 with SQL 2012 Express to a new server running SQL Server 2017 Standard and Windows 2016. I would like to mirror databases between them, but the Express Edition doesn't support it. I tried to upgrade it to SQL 2012 Standard Evaluation, but I received the following error:
Failed The selected SQL Server instance does not
meet upgrade matrix requirements.
I discovered this isn't possible:
Upgrade SQL Server 2012 Express to Evaluation Edition
I was forced to install SQL Server 2012 Evaluation as a new side-by-side instance and named it ./SQLSERVER2. In order to use this instance, however, it would require moving a ton of data files and changing the instance names in all my configuration files. This will also require server downtime as well. This will be a major PITA without the humous and I want to avoid it if at all possible.
Is there a way of reconfiguring ./SQLSERVER to use the Standard Evaluation Edition with minimal downtime and side-effects?
sql-server upgrade mirroring instance
sql-server upgrade mirroring instance
edited Oct 26 '18 at 5:55
Colin 't Hart
6,63682634
asked Oct 26 '18 at 4:31
ATL_DEVATL_DEV
1011
edited Oct 26 '18 at 5:55
Colin 't Hart
6,63682634
asked Oct 26 '18 at 4:31
ATL_DEVATL_DEV
1011
edited Oct 26 '18 at 5:55
Colin 't Hart
6,63682634
edited Oct 26 '18 at 5:55
Colin 't Hart
6,63682634
edited Oct 26 '18 at 5:55
Colin 't Hart
6,63682634
6,63682634
asked Oct 26 '18 at 4:31
ATL_DEVATL_DEV
1011
asked Oct 26 '18 at 4:31
ATL_DEVATL_DEV
1011
asked Oct 26 '18 at 4:31
ATL_DEVATL_DEV
1011
1011
bumped to the homepage by Community♦ 13 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♦ 13 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Install them side by side, then backup the database from Express Edition and restore it to Standard Edition.
– Randolph West
Oct 26 '18 at 21:31
add a comment |
Install them side by side, then backup the database from Express Edition and restore it to Standard Edition.
– Randolph West
Oct 26 '18 at 21:31
Install them side by side, then backup the database from Express Edition and restore it to Standard Edition.
– Randolph West
Oct 26 '18 at 21:31
Install them side by side, then backup the database from Express Edition and restore it to Standard Edition.
– Randolph West
Oct 26 '18 at 21:31
add a comment |
1 Answer
1
active
oldest
votes
For the sake of providing help to others who encounter this terrifying scenario, you can't use the Evaluation to perform an inplace upgrade. Microsoft buries this deep in their mazing documentation (not a misspelling, mazing as in maze).
I got tangled in Microsoft's web where I couldn't perform an inplace upgrade from SQL 2012 to 2017 because Windows 2008 Server can't run SQL 2017. I also couldn't upgrade to SQL 2012 Developer either, since it was artificially prohibited like the Evaluation version.
Thus, I was forced to update to SQL 2012 Standard Edition, which requires another license. Fortunately, I discovered we already had a license. I originally opted to install the Express Edition because it had a smaller footprint and we didn't need the extra bulk.
Microsoft deliberately designed the SQL upgrade path to try to extort a license from their customers. Either you obtain a license key for SQL 2012 Standard or upgrade your server. Neat trick, huh? I wasn't about to do either, since I was decommissioning the old server.
answered Oct 27 '18 at 21:19
ATL_DEVATL_DEV
1011
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%2f221056%2fhow-do-i-configure-my-sql-server-instance-to-use-a-different-edition-with-minima%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 the sake of providing help to others who encounter this terrifying scenario, you can't use the Evaluation to perform an inplace upgrade. Microsoft buries this deep in their mazing documentation (not a misspelling, mazing as in maze).
I got tangled in Microsoft's web where I couldn't perform an inplace upgrade from SQL 2012 to 2017 because Windows 2008 Server can't run SQL 2017. I also couldn't upgrade to SQL 2012 Developer either, since it was artificially prohibited like the Evaluation version.
Thus, I was forced to update to SQL 2012 Standard Edition, which requires another license. Fortunately, I discovered we already had a license. I originally opted to install the Express Edition because it had a smaller footprint and we didn't need the extra bulk.
Microsoft deliberately designed the SQL upgrade path to try to extort a license from their customers. Either you obtain a license key for SQL 2012 Standard or upgrade your server. Neat trick, huh? I wasn't about to do either, since I was decommissioning the old server.
answered Oct 27 '18 at 21:19
ATL_DEVATL_DEV
1011
add a comment |
For the sake of providing help to others who encounter this terrifying scenario, you can't use the Evaluation to perform an inplace upgrade. Microsoft buries this deep in their mazing documentation (not a misspelling, mazing as in maze).
I got tangled in Microsoft's web where I couldn't perform an inplace upgrade from SQL 2012 to 2017 because Windows 2008 Server can't run SQL 2017. I also couldn't upgrade to SQL 2012 Developer either, since it was artificially prohibited like the Evaluation version.
Thus, I was forced to update to SQL 2012 Standard Edition, which requires another license. Fortunately, I discovered we already had a license. I originally opted to install the Express Edition because it had a smaller footprint and we didn't need the extra bulk.
Microsoft deliberately designed the SQL upgrade path to try to extort a license from their customers. Either you obtain a license key for SQL 2012 Standard or upgrade your server. Neat trick, huh? I wasn't about to do either, since I was decommissioning the old server.
answered Oct 27 '18 at 21:19
ATL_DEVATL_DEV
1011
add a comment |
For the sake of providing help to others who encounter this terrifying scenario, you can't use the Evaluation to perform an inplace upgrade. Microsoft buries this deep in their mazing documentation (not a misspelling, mazing as in maze).
I got tangled in Microsoft's web where I couldn't perform an inplace upgrade from SQL 2012 to 2017 because Windows 2008 Server can't run SQL 2017. I also couldn't upgrade to SQL 2012 Developer either, since it was artificially prohibited like the Evaluation version.
Thus, I was forced to update to SQL 2012 Standard Edition, which requires another license. Fortunately, I discovered we already had a license. I originally opted to install the Express Edition because it had a smaller footprint and we didn't need the extra bulk.
Microsoft deliberately designed the SQL upgrade path to try to extort a license from their customers. Either you obtain a license key for SQL 2012 Standard or upgrade your server. Neat trick, huh? I wasn't about to do either, since I was decommissioning the old server.
answered Oct 27 '18 at 21:19
ATL_DEVATL_DEV
1011
For the sake of providing help to others who encounter this terrifying scenario, you can't use the Evaluation to perform an inplace upgrade. Microsoft buries this deep in their mazing documentation (not a misspelling, mazing as in maze).
I got tangled in Microsoft's web where I couldn't perform an inplace upgrade from SQL 2012 to 2017 because Windows 2008 Server can't run SQL 2017. I also couldn't upgrade to SQL 2012 Developer either, since it was artificially prohibited like the Evaluation version.
Thus, I was forced to update to SQL 2012 Standard Edition, which requires another license. Fortunately, I discovered we already had a license. I originally opted to install the Express Edition because it had a smaller footprint and we didn't need the extra bulk.
Microsoft deliberately designed the SQL upgrade path to try to extort a license from their customers. Either you obtain a license key for SQL 2012 Standard or upgrade your server. Neat trick, huh? I wasn't about to do either, since I was decommissioning the old server.
answered Oct 27 '18 at 21:19
ATL_DEVATL_DEV
1011
edited Nov 4 '18 at 21:28
answered Oct 27 '18 at 21:19
ATL_DEVATL_DEV
1011
answered Oct 27 '18 at 21:19
ATL_DEVATL_DEV
1011
answered Oct 27 '18 at 21:19
ATL_DEVATL_DEV
1011
1011
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%2f221056%2fhow-do-i-configure-my-sql-server-instance-to-use-a-different-edition-with-minima%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
Install them side by side, then backup the database from Express Edition and restore it to Standard Edition.
– Randolph West
Oct 26 '18 at 21:31