New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CheckDB Snapshots in other location #181

Open
RGarciaSQ opened this Issue Dec 24, 2018 · 1 comment

Comments

2 participants
@RGarciaSQ
Copy link

RGarciaSQ commented Dec 24, 2018

The use case is that in a Data drive with few space available, as CHECKDB operations create a snapshot of the databases in the drive and checks that instead, the problem is that there if there is not enough space available in the drive for the snapshot to generate operation will fail.

Could it be possible to add to generate DB snapshot manually in other location and perform the operation over it and then delete it as a feature to scripts? Maybe a param @SnapshotLocation to specify it needs to create it in other location and then execute the command.

@olahallengren

This comment has been minimized.

Copy link
Owner

olahallengren commented Dec 29, 2018

This is a good idea. The risk is just that if the job is getting aborted for some reason, then the snapshot will not be deleted.

The best would be if Microsoft could add an option to the CHECKDB command, where the snapshots should be created. Please vote for this idea on UserVoice.

https://feedback.azure.com/forums/908035-sql-server/suggestions/36206044-option-to-specify-a-location-for-the-dbcc-checkdb

Then I would also add support for it in my scripts.

@olahallengren olahallengren changed the title Feature Request - CheckDB Snapshots in other location CheckDB Snapshots in other location Dec 30, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment