Transparent Data Encryption with SQL Server 2016 causing drive space issue
0
We are attempting to use TDE with SQL Server 2016 to encrypt a large database. However, when the encryption gets to about 91% we receive a drive space error and the encryption fails. Being that TDE does not cause an increase in the database size, would someone be able to tell me why this is happening?
My only assumption is that a copy of the DB is being encrypted and then the non-encrypted version is being dropped as part of the process. Which means we need to ensure that we have enough available space on the drive to support two .mdf files for the single database. Any insight would be greatly appreciated.
encryption sql-server-2016 tde
edited Nov 26 '18 at 21:23
marc_s
577k12911151260
asked Nov 26 '18 at 21:21
JSanbornJSanborn
263
add a comment |
0
We are attempting to use TDE with SQL Server 2016 to encrypt a large database. However, when the encryption gets to about 91% we receive a drive space error and the encryption fails. Being that TDE does not cause an increase in the database size, would someone be able to tell me why this is happening?
My only assumption is that a copy of the DB is being encrypted and then the non-encrypted version is being dropped as part of the process. Which means we need to ensure that we have enough available space on the drive to support two .mdf files for the single database. Any insight would be greatly appreciated.
encryption sql-server-2016 tde
edited Nov 26 '18 at 21:23
marc_s
577k12911151260
asked Nov 26 '18 at 21:21
JSanbornJSanborn
263
Kick off the TDE operation and then watch the log space. If you fill up the log, the transaction will fail and rollback. If it is not a log failure, then increase the drive size. Space is cheap nowadays.
– dfundako
Nov 26 '18 at 21:23
The issue is the drive that holds the .mdf files is running out of space during the encryption process. The database is about 550GB and there is about 350GB of space left on the drive, during the encryption process, our monitor shows that they 350GB drops to 1MB and causes the operation to fail. The drive for the log files is not the issue. Hope that clarifies a little.
– JSanborn
Nov 26 '18 at 21:32
Also, I understand storage is inexpensive, but I would like to understand why the file space is growing when it shouldn't be.
– JSanborn
Nov 26 '18 at 21:46
So, do your DB still work after 91% encryption ? If it does, it properbly worked on a copy of the DB .. The size not increasing refers to the feature when being operational.
– Ebbe M. Pedersen
Nov 27 '18 at 9:00
The database is not functional after 91% encryption. We had to drop the database and restore from the snapshot taken before the encryption. I think we need to investigate a little further. I was able to process the encryption and decryption of the same database locally without any issues. I had way less space available and still no issues. There must be something else going on that we have been able to determine at this time. Thank you for you assistance.
– JSanborn
Nov 27 '18 at 14:59
add a comment |
0
0
0
We are attempting to use TDE with SQL Server 2016 to encrypt a large database. However, when the encryption gets to about 91% we receive a drive space error and the encryption fails. Being that TDE does not cause an increase in the database size, would someone be able to tell me why this is happening?
My only assumption is that a copy of the DB is being encrypted and then the non-encrypted version is being dropped as part of the process. Which means we need to ensure that we have enough available space on the drive to support two .mdf files for the single database. Any insight would be greatly appreciated.
encryption sql-server-2016 tde
edited Nov 26 '18 at 21:23
marc_s
577k12911151260
asked Nov 26 '18 at 21:21
JSanbornJSanborn
263
We are attempting to use TDE with SQL Server 2016 to encrypt a large database. However, when the encryption gets to about 91% we receive a drive space error and the encryption fails. Being that TDE does not cause an increase in the database size, would someone be able to tell me why this is happening?
My only assumption is that a copy of the DB is being encrypted and then the non-encrypted version is being dropped as part of the process. Which means we need to ensure that we have enough available space on the drive to support two .mdf files for the single database. Any insight would be greatly appreciated.
encryption sql-server-2016 tde
encryption sql-server-2016 tde
edited Nov 26 '18 at 21:23
marc_s
577k12911151260
asked Nov 26 '18 at 21:21
JSanbornJSanborn
263
edited Nov 26 '18 at 21:23
marc_s
577k12911151260
asked Nov 26 '18 at 21:21
JSanbornJSanborn
263
edited Nov 26 '18 at 21:23
marc_s
577k12911151260
edited Nov 26 '18 at 21:23
marc_s
577k12911151260
edited Nov 26 '18 at 21:23
marc_s
577k12911151260
577k12911151260
asked Nov 26 '18 at 21:21
JSanbornJSanborn
263
asked Nov 26 '18 at 21:21
JSanbornJSanborn
263
asked Nov 26 '18 at 21:21
JSanbornJSanborn
263
263
Kick off the TDE operation and then watch the log space. If you fill up the log, the transaction will fail and rollback. If it is not a log failure, then increase the drive size. Space is cheap nowadays.
– dfundako
Nov 26 '18 at 21:23
The issue is the drive that holds the .mdf files is running out of space during the encryption process. The database is about 550GB and there is about 350GB of space left on the drive, during the encryption process, our monitor shows that they 350GB drops to 1MB and causes the operation to fail. The drive for the log files is not the issue. Hope that clarifies a little.
– JSanborn
Nov 26 '18 at 21:32
Also, I understand storage is inexpensive, but I would like to understand why the file space is growing when it shouldn't be.
– JSanborn
Nov 26 '18 at 21:46
So, do your DB still work after 91% encryption ? If it does, it properbly worked on a copy of the DB .. The size not increasing refers to the feature when being operational.
– Ebbe M. Pedersen
Nov 27 '18 at 9:00
The database is not functional after 91% encryption. We had to drop the database and restore from the snapshot taken before the encryption. I think we need to investigate a little further. I was able to process the encryption and decryption of the same database locally without any issues. I had way less space available and still no issues. There must be something else going on that we have been able to determine at this time. Thank you for you assistance.
– JSanborn
Nov 27 '18 at 14:59
add a comment |
Kick off the TDE operation and then watch the log space. If you fill up the log, the transaction will fail and rollback. If it is not a log failure, then increase the drive size. Space is cheap nowadays.
– dfundako
Nov 26 '18 at 21:23
The issue is the drive that holds the .mdf files is running out of space during the encryption process. The database is about 550GB and there is about 350GB of space left on the drive, during the encryption process, our monitor shows that they 350GB drops to 1MB and causes the operation to fail. The drive for the log files is not the issue. Hope that clarifies a little.
– JSanborn
Nov 26 '18 at 21:32
Also, I understand storage is inexpensive, but I would like to understand why the file space is growing when it shouldn't be.
– JSanborn
Nov 26 '18 at 21:46
So, do your DB still work after 91% encryption ? If it does, it properbly worked on a copy of the DB .. The size not increasing refers to the feature when being operational.
– Ebbe M. Pedersen
Nov 27 '18 at 9:00
The database is not functional after 91% encryption. We had to drop the database and restore from the snapshot taken before the encryption. I think we need to investigate a little further. I was able to process the encryption and decryption of the same database locally without any issues. I had way less space available and still no issues. There must be something else going on that we have been able to determine at this time. Thank you for you assistance.
– JSanborn
Nov 27 '18 at 14:59
Kick off the TDE operation and then watch the log space. If you fill up the log, the transaction will fail and rollback. If it is not a log failure, then increase the drive size. Space is cheap nowadays.
– dfundako
Nov 26 '18 at 21:23
Kick off the TDE operation and then watch the log space. If you fill up the log, the transaction will fail and rollback. If it is not a log failure, then increase the drive size. Space is cheap nowadays.
– dfundako
Nov 26 '18 at 21:23
The issue is the drive that holds the .mdf files is running out of space during the encryption process. The database is about 550GB and there is about 350GB of space left on the drive, during the encryption process, our monitor shows that they 350GB drops to 1MB and causes the operation to fail. The drive for the log files is not the issue. Hope that clarifies a little.
– JSanborn
Nov 26 '18 at 21:32
The issue is the drive that holds the .mdf files is running out of space during the encryption process. The database is about 550GB and there is about 350GB of space left on the drive, during the encryption process, our monitor shows that they 350GB drops to 1MB and causes the operation to fail. The drive for the log files is not the issue. Hope that clarifies a little.
– JSanborn
Nov 26 '18 at 21:32
Also, I understand storage is inexpensive, but I would like to understand why the file space is growing when it shouldn't be.
– JSanborn
Nov 26 '18 at 21:46
Also, I understand storage is inexpensive, but I would like to understand why the file space is growing when it shouldn't be.
– JSanborn
Nov 26 '18 at 21:46
So, do your DB still work after 91% encryption ? If it does, it properbly worked on a copy of the DB .. The size not increasing refers to the feature when being operational.
– Ebbe M. Pedersen
Nov 27 '18 at 9:00
So, do your DB still work after 91% encryption ? If it does, it properbly worked on a copy of the DB .. The size not increasing refers to the feature when being operational.
– Ebbe M. Pedersen
Nov 27 '18 at 9:00
The database is not functional after 91% encryption. We had to drop the database and restore from the snapshot taken before the encryption. I think we need to investigate a little further. I was able to process the encryption and decryption of the same database locally without any issues. I had way less space available and still no issues. There must be something else going on that we have been able to determine at this time. Thank you for you assistance.
– JSanborn
Nov 27 '18 at 14:59
The database is not functional after 91% encryption. We had to drop the database and restore from the snapshot taken before the encryption. I think we need to investigate a little further. I was able to process the encryption and decryption of the same database locally without any issues. I had way less space available and still no issues. There must be something else going on that we have been able to determine at this time. Thank you for you assistance.
– JSanborn
Nov 27 '18 at 14:59
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});
}
});
draft saved
draft discarded
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%2fstackoverflow.com%2fquestions%2f53489249%2ftransparent-data-encryption-with-sql-server-2016-causing-drive-space-issue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- 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.
draft saved
draft discarded
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%2fstackoverflow.com%2fquestions%2f53489249%2ftransparent-data-encryption-with-sql-server-2016-causing-drive-space-issue%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
Kick off the TDE operation and then watch the log space. If you fill up the log, the transaction will fail and rollback. If it is not a log failure, then increase the drive size. Space is cheap nowadays.
– dfundako
Nov 26 '18 at 21:23
The issue is the drive that holds the .mdf files is running out of space during the encryption process. The database is about 550GB and there is about 350GB of space left on the drive, during the encryption process, our monitor shows that they 350GB drops to 1MB and causes the operation to fail. The drive for the log files is not the issue. Hope that clarifies a little.
– JSanborn
Nov 26 '18 at 21:32
Also, I understand storage is inexpensive, but I would like to understand why the file space is growing when it shouldn't be.
– JSanborn
Nov 26 '18 at 21:46
So, do your DB still work after 91% encryption ? If it does, it properbly worked on a copy of the DB .. The size not increasing refers to the feature when being operational.
– Ebbe M. Pedersen
Nov 27 '18 at 9:00
The database is not functional after 91% encryption. We had to drop the database and restore from the snapshot taken before the encryption. I think we need to investigate a little further. I was able to process the encryption and decryption of the same database locally without any issues. I had way less space available and still no issues. There must be something else going on that we have been able to determine at this time. Thank you for you assistance.
– JSanborn
Nov 27 '18 at 14:59