Add support for new SQL Server 2022 snapshot backup / restore functionality

未关闭
#39 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
sql
领域
databases

调研方向

从 issue 中链接的 SQL Server 快照备份文档开始,并将其中的示例与 ScriptDOM 当前的解析行为进行比较。检查列出的 ALTER DATABASE、ALTER SERVER CONFIGURATION、BACKUP 和 RESTORE 语句,包括它们的新选项。当所示的快照备份和还原语法能够被 ScriptDOM 识别,且不会与数据库快照混淆时,即视为完成。

由索引模型根据 Issue 内容生成。

描述

enhancement sql-feature

SQL Server 2022 introduced a new type of backup - snapshot. ScriptDom currently does not support this type of backup. Note that this is different from the database snapshot functionality, which has been around since SQL Server 2005. In addition, there are new statements (BACKUP GROUP and BACKUP SERVER) in SQL Server 2022 which work in conjunction with these snapshot backups. There are also new options like SUSPEND_FOR_SNAPSHOT_BACKUP for ALTER DATABASE and ALTER SERVER CONFIGURATION, which are not recognized by ScriptDom. Example of statements which should be handled by ScriptDom are below. There are more examples in the docs linked to earlier.

ALTER DATABASE testdb1
SET SUSPEND_FOR_SNAPSHOT_BACKUP = ON
(MODE = COPY_ONLY);

ALTER SERVER CONFIGURATION
SET SUSPEND_FOR_SNAPSHOT_BACKUP = ON
(GROUP = (testdb1, testdb2), MODE = COPY_ONLY);

BACKUP DATABASE testdb1
TO DISK = 'd:\temp\db.bkm'
WITH METADATA_ONLY, FORMAT;

RESTORE DATABASE testdb1
FROM DISK = 'd:\temp\db.bkm'
WITH METADATA_ONLY, FILE = 3, REPLACE, --> no DBNAME clause - restore first database in backup set
MOVE 'testdb1' TO 'd:\temp\snap\testdb1.mdf',
MOVE 'testdb1_log' TO 'd:\temp\snap\testdb1_log.ldf';
主要语言
GAP
星标
277
派生
43
平均合并
6 天 17 小时
30 天内合并 PR
3

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

microsoft/SqlScriptDOM 的其他 Issue

查看 microsoft/SqlScriptDOM 的全部 Issue

相似的 Issue

更多 Databases Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。