Azure SQL DWH delete and restore it when requires

Is there an option to restore the deleted database in SQL DWH at a later time(more than a year )?

asked Nov 14 '18 at 9:03

shiva k

I'm planning to delete a database on SQL DWH. But if requires I need to restore the database. Need to get confirmation about this.

– shiva k
Nov 14 '18 at 9:05

I suggest you read the produce documentation docs.microsoft.com/en-us/azure/sql-data-warehouse/…

– Nick.McDermaid
Nov 14 '18 at 9:20

Thanks, @Nick.McDermaid for responding. The problem is I came across another document (docs.microsoft.com/en-us/azure/sql-data-warehouse/…) where there is an option to restore the deleted database. But in the document which you mentioned, it is different. I've asked this question to get confirmation from a person who restored the deleted database in SQLDWH.

– shiva k
Nov 14 '18 at 10:26

add a comment |

Is there an option to restore the deleted database in SQL DWH at a later time(more than a year )?

asked Nov 14 '18 at 9:03

shiva k

I'm planning to delete a database on SQL DWH. But if requires I need to restore the database. Need to get confirmation about this.

– shiva k
Nov 14 '18 at 9:05

I suggest you read the produce documentation docs.microsoft.com/en-us/azure/sql-data-warehouse/…

– Nick.McDermaid
Nov 14 '18 at 9:20

Thanks, @Nick.McDermaid for responding. The problem is I came across another document (docs.microsoft.com/en-us/azure/sql-data-warehouse/…) where there is an option to restore the deleted database. But in the document which you mentioned, it is different. I've asked this question to get confirmation from a person who restored the deleted database in SQLDWH.

– shiva k
Nov 14 '18 at 10:26

add a comment |

Is there an option to restore the deleted database in SQL DWH at a later time(more than a year )?

asked Nov 14 '18 at 9:03

shiva k

Is there an option to restore the deleted database in SQL DWH at a later time(more than a year )?

azure-sqldw

asked Nov 14 '18 at 9:03

shiva k

asked Nov 14 '18 at 9:03

shiva k

asked Nov 14 '18 at 9:03

shiva k

asked Nov 14 '18 at 9:03

shiva k

asked Nov 14 '18 at 9:03

shiva k

I'm planning to delete a database on SQL DWH. But if requires I need to restore the database. Need to get confirmation about this.

– shiva k
Nov 14 '18 at 9:05

I suggest you read the produce documentation docs.microsoft.com/en-us/azure/sql-data-warehouse/…

– Nick.McDermaid
Nov 14 '18 at 9:20

Thanks, @Nick.McDermaid for responding. The problem is I came across another document (docs.microsoft.com/en-us/azure/sql-data-warehouse/…) where there is an option to restore the deleted database. But in the document which you mentioned, it is different. I've asked this question to get confirmation from a person who restored the deleted database in SQLDWH.

– shiva k
Nov 14 '18 at 10:26

add a comment |

I'm planning to delete a database on SQL DWH. But if requires I need to restore the database. Need to get confirmation about this.

– shiva k
Nov 14 '18 at 9:05

I suggest you read the produce documentation docs.microsoft.com/en-us/azure/sql-data-warehouse/…

– Nick.McDermaid
Nov 14 '18 at 9:20

Thanks, @Nick.McDermaid for responding. The problem is I came across another document (docs.microsoft.com/en-us/azure/sql-data-warehouse/…) where there is an option to restore the deleted database. But in the document which you mentioned, it is different. I've asked this question to get confirmation from a person who restored the deleted database in SQLDWH.

– shiva k
Nov 14 '18 at 10:26

I'm planning to delete a database on SQL DWH. But if requires I need to restore the database. Need to get confirmation about this.

– shiva k
Nov 14 '18 at 9:05

I suggest you read the produce documentation docs.microsoft.com/en-us/azure/sql-data-warehouse/…

– Nick.McDermaid
Nov 14 '18 at 9:20

Thanks, @Nick.McDermaid for responding. The problem is I came across another document (docs.microsoft.com/en-us/azure/sql-data-warehouse/…) where there is an option to restore the deleted database. But in the document which you mentioned, it is different. I've asked this question to get confirmation from a person who restored the deleted database in SQLDWH.

– shiva k
Nov 14 '18 at 10:26

add a comment |

1 Answer
1

active

oldest

votes

The documentation clearly indicates that when an Azure SQL Data Warehouse is dropped it keeps the final snapshot for seven days:

When you drop a data warehouse, SQL Data Warehouse creates a final
snapshot and saves it for seven days. You can restore the data
warehouse to the final restore point created at deletion.

The same article also mentions the fact you can vote for this feature here:
https://feedback.azure.com/forums/307516-sql-data-warehouse/suggestions/35114410-user-defined-retention-periods-for-restore-points

Even if you could do this, you are basically leaving it up to someone else to be in charge of your warehouse backups. What you could do instead is take control:

Store your Azure SQL Data Warehouse schema in source code control (eg git, Azure DevOps formerly VSTS, etc). If it isn't there already you can reverse engineer the schema using SQL Server Management Studio (SSMS) versions 17.x onwards or even use the SSDT preview feature

Export your data to Data Lake or Azure Blob Storage using CREATE EXTERNAL TABLE AS SELECT (CETAS). This will export your data as flat files to storage where it won't be deleted. Alternately use Azure Data Factory to export the data and zip it up to save space.

When you need to recreate the warehouse, simply redeploy the schema from source code control and redeploy the data, eg via CTAS in to staging tables, or use Azure Data Factory to re-import. If you saved your external tables in the schema you save to source code control then it will just be there when you redeploy. INSERT back in to the main tables from the external tables.

In this way you are in charge of your warehouse schema and your data to be recreated at any point you require, whether it be a day, a month or years.

A simple diagram of the proposed design:
adw support diagram

edited Nov 14 '18 at 11:24

answered Nov 14 '18 at 10:56

wBob

5,76931022

Any constructive feedback @JRJ?

– wBob
Nov 14 '18 at 11:25

add a comment |

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');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53296382%2fazure-sql-dwh-delete-and-restore-it-when-requires%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

The documentation clearly indicates that when an Azure SQL Data Warehouse is dropped it keeps the final snapshot for seven days:

When you drop a data warehouse, SQL Data Warehouse creates a final
snapshot and saves it for seven days. You can restore the data
warehouse to the final restore point created at deletion.

Even if you could do this, you are basically leaving it up to someone else to be in charge of your warehouse backups. What you could do instead is take control:

Store your Azure SQL Data Warehouse schema in source code control (eg git, Azure DevOps formerly VSTS, etc). If it isn't there already you can reverse engineer the schema using SQL Server Management Studio (SSMS) versions 17.x onwards or even use the SSDT preview feature

Export your data to Data Lake or Azure Blob Storage using CREATE EXTERNAL TABLE AS SELECT (CETAS). This will export your data as flat files to storage where it won't be deleted. Alternately use Azure Data Factory to export the data and zip it up to save space.

When you need to recreate the warehouse, simply redeploy the schema from source code control and redeploy the data, eg via CTAS in to staging tables, or use Azure Data Factory to re-import. If you saved your external tables in the schema you save to source code control then it will just be there when you redeploy. INSERT back in to the main tables from the external tables.

In this way you are in charge of your warehouse schema and your data to be recreated at any point you require, whether it be a day, a month or years.

A simple diagram of the proposed design:
adw support diagram

edited Nov 14 '18 at 11:24

answered Nov 14 '18 at 10:56

wBob

5,76931022

Any constructive feedback @JRJ?

– wBob
Nov 14 '18 at 11:25

add a comment |

The documentation clearly indicates that when an Azure SQL Data Warehouse is dropped it keeps the final snapshot for seven days:

When you drop a data warehouse, SQL Data Warehouse creates a final
snapshot and saves it for seven days. You can restore the data
warehouse to the final restore point created at deletion.

Even if you could do this, you are basically leaving it up to someone else to be in charge of your warehouse backups. What you could do instead is take control:

Store your Azure SQL Data Warehouse schema in source code control (eg git, Azure DevOps formerly VSTS, etc). If it isn't there already you can reverse engineer the schema using SQL Server Management Studio (SSMS) versions 17.x onwards or even use the SSDT preview feature

Export your data to Data Lake or Azure Blob Storage using CREATE EXTERNAL TABLE AS SELECT (CETAS). This will export your data as flat files to storage where it won't be deleted. Alternately use Azure Data Factory to export the data and zip it up to save space.

When you need to recreate the warehouse, simply redeploy the schema from source code control and redeploy the data, eg via CTAS in to staging tables, or use Azure Data Factory to re-import. If you saved your external tables in the schema you save to source code control then it will just be there when you redeploy. INSERT back in to the main tables from the external tables.

In this way you are in charge of your warehouse schema and your data to be recreated at any point you require, whether it be a day, a month or years.

A simple diagram of the proposed design:
adw support diagram

edited Nov 14 '18 at 11:24

answered Nov 14 '18 at 10:56

wBob

5,76931022

Any constructive feedback @JRJ?

– wBob
Nov 14 '18 at 11:25

add a comment |

The documentation clearly indicates that when an Azure SQL Data Warehouse is dropped it keeps the final snapshot for seven days:

When you drop a data warehouse, SQL Data Warehouse creates a final
snapshot and saves it for seven days. You can restore the data
warehouse to the final restore point created at deletion.

Even if you could do this, you are basically leaving it up to someone else to be in charge of your warehouse backups. What you could do instead is take control:

Store your Azure SQL Data Warehouse schema in source code control (eg git, Azure DevOps formerly VSTS, etc). If it isn't there already you can reverse engineer the schema using SQL Server Management Studio (SSMS) versions 17.x onwards or even use the SSDT preview feature

Export your data to Data Lake or Azure Blob Storage using CREATE EXTERNAL TABLE AS SELECT (CETAS). This will export your data as flat files to storage where it won't be deleted. Alternately use Azure Data Factory to export the data and zip it up to save space.

When you need to recreate the warehouse, simply redeploy the schema from source code control and redeploy the data, eg via CTAS in to staging tables, or use Azure Data Factory to re-import. If you saved your external tables in the schema you save to source code control then it will just be there when you redeploy. INSERT back in to the main tables from the external tables.

In this way you are in charge of your warehouse schema and your data to be recreated at any point you require, whether it be a day, a month or years.

A simple diagram of the proposed design:
adw support diagram

edited Nov 14 '18 at 11:24

answered Nov 14 '18 at 10:56

wBob

5,76931022

The documentation clearly indicates that when an Azure SQL Data Warehouse is dropped it keeps the final snapshot for seven days:

When you drop a data warehouse, SQL Data Warehouse creates a final
snapshot and saves it for seven days. You can restore the data
warehouse to the final restore point created at deletion.

Even if you could do this, you are basically leaving it up to someone else to be in charge of your warehouse backups. What you could do instead is take control:

Store your Azure SQL Data Warehouse schema in source code control (eg git, Azure DevOps formerly VSTS, etc). If it isn't there already you can reverse engineer the schema using SQL Server Management Studio (SSMS) versions 17.x onwards or even use the SSDT preview feature

Export your data to Data Lake or Azure Blob Storage using CREATE EXTERNAL TABLE AS SELECT (CETAS). This will export your data as flat files to storage where it won't be deleted. Alternately use Azure Data Factory to export the data and zip it up to save space.

When you need to recreate the warehouse, simply redeploy the schema from source code control and redeploy the data, eg via CTAS in to staging tables, or use Azure Data Factory to re-import. If you saved your external tables in the schema you save to source code control then it will just be there when you redeploy. INSERT back in to the main tables from the external tables.

In this way you are in charge of your warehouse schema and your data to be recreated at any point you require, whether it be a day, a month or years.

A simple diagram of the proposed design:
adw support diagram

edited Nov 14 '18 at 11:24

answered Nov 14 '18 at 10:56

wBob

5,76931022

edited Nov 14 '18 at 11:24

answered Nov 14 '18 at 10:56

wBob

5,76931022

answered Nov 14 '18 at 10:56

wBob

5,76931022

answered Nov 14 '18 at 10:56

wBob

5,76931022

Any constructive feedback @JRJ?

– wBob
Nov 14 '18 at 11:25

add a comment |

Any constructive feedback @JRJ?

– wBob
Nov 14 '18 at 11:25

Any constructive feedback @JRJ?

– wBob
Nov 14 '18 at 11:25

add a comment |

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');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Wsrtjtyk