Use a SP to Archive/Revision related records in several related tables?
I have a database for an application that has a complicated relational table structure. Is there a good way to create revisions of the data, or archive the data before a user makes changes?
Ideally I would want a stored procedure that would save the state of all the related data when ran, insomuch that when a field is added to any of the related tables, the stored procedure would not miss it.
sql-server stored-procedures archive
asked Jan 15 '16 at 20:08
Pratt HindsPratt Hinds
161
bumped to the homepage by Community♦ 22 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 have a database for an application that has a complicated relational table structure. Is there a good way to create revisions of the data, or archive the data before a user makes changes?
Ideally I would want a stored procedure that would save the state of all the related data when ran, insomuch that when a field is added to any of the related tables, the stored procedure would not miss it.
sql-server stored-procedures archive
asked Jan 15 '16 at 20:08
Pratt HindsPratt Hinds
161
bumped to the homepage by Community♦ 22 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
1
depending on the version of sql server you are .. you can look into change data capture or change tracking. That will help you.
– Kin
Jan 15 '16 at 21:25
2
Are you talking about structural changes to your database as in DDL changes? Or are you talking about a user updating a particular row, DML?
– Zane
Jan 15 '16 at 21:41
1
Are you thinking of implementing a temporal database, where each value has a datetime range when it is the effective value, and all past values are also retained?
– Michael Green
Jan 16 '16 at 7:15
add a comment |
I have a database for an application that has a complicated relational table structure. Is there a good way to create revisions of the data, or archive the data before a user makes changes?
Ideally I would want a stored procedure that would save the state of all the related data when ran, insomuch that when a field is added to any of the related tables, the stored procedure would not miss it.
sql-server stored-procedures archive
asked Jan 15 '16 at 20:08
Pratt HindsPratt Hinds
161
I have a database for an application that has a complicated relational table structure. Is there a good way to create revisions of the data, or archive the data before a user makes changes?
Ideally I would want a stored procedure that would save the state of all the related data when ran, insomuch that when a field is added to any of the related tables, the stored procedure would not miss it.
sql-server stored-procedures archive
sql-server stored-procedures archive
asked Jan 15 '16 at 20:08
Pratt HindsPratt Hinds
161
asked Jan 15 '16 at 20:08
Pratt HindsPratt Hinds
161
asked Jan 15 '16 at 20:08
Pratt HindsPratt Hinds
161
asked Jan 15 '16 at 20:08
Pratt HindsPratt Hinds
161
asked Jan 15 '16 at 20:08
Pratt HindsPratt Hinds
161
161
bumped to the homepage by Community♦ 22 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♦ 22 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
1
depending on the version of sql server you are .. you can look into change data capture or change tracking. That will help you.
– Kin
Jan 15 '16 at 21:25
2
Are you talking about structural changes to your database as in DDL changes? Or are you talking about a user updating a particular row, DML?
– Zane
Jan 15 '16 at 21:41
1
Are you thinking of implementing a temporal database, where each value has a datetime range when it is the effective value, and all past values are also retained?
– Michael Green
Jan 16 '16 at 7:15
add a comment |
1
depending on the version of sql server you are .. you can look into change data capture or change tracking. That will help you.
– Kin
Jan 15 '16 at 21:25
2
Are you talking about structural changes to your database as in DDL changes? Or are you talking about a user updating a particular row, DML?
– Zane
Jan 15 '16 at 21:41
1
Are you thinking of implementing a temporal database, where each value has a datetime range when it is the effective value, and all past values are also retained?
– Michael Green
Jan 16 '16 at 7:15
1
1
depending on the version of sql server you are .. you can look into change data capture or change tracking. That will help you.
– Kin
Jan 15 '16 at 21:25
depending on the version of sql server you are .. you can look into change data capture or change tracking. That will help you.
– Kin
Jan 15 '16 at 21:25
2
2
Are you talking about structural changes to your database as in DDL changes? Or are you talking about a user updating a particular row, DML?
– Zane
Jan 15 '16 at 21:41
Are you talking about structural changes to your database as in DDL changes? Or are you talking about a user updating a particular row, DML?
– Zane
Jan 15 '16 at 21:41
1
1
Are you thinking of implementing a temporal database, where each value has a datetime range when it is the effective value, and all past values are also retained?
– Michael Green
Jan 16 '16 at 7:15
Are you thinking of implementing a temporal database, where each value has a datetime range when it is the effective value, and all past values are also retained?
– Michael Green
Jan 16 '16 at 7:15
add a comment |
1 Answer
1
active
oldest
votes
Creating such a stored procedure is probably going to be complex and error prone. That's why there are temporal databases or temporal features in a database. If you really wanted to do this with a stored procedure, you can have a duplicate schema with a version number column added to all tables.
That way, on each write operation, you can first call the stored procedure which does an INSERT INTO.... SELECT using the same WHERE clause as your write operation. The stored procedure is best initiated by the app which runs the stored procedure before the actual write (UPDATE/DELETE) statement.
If you use triggers, it can be very tricky just figuring out which table(s) to host the trigger and making sure you don't get a trigger storm.
Far easier path is to implement something like Temporal tables in SQL Server 2016: https://msdn.microsoft.com/en-us/library/dn935015.aspx. Takes a bit of work to setup but it's only somewhat tedious work, not very complex work. If you want to keep this history around for a long time, you can even stretch the temporal history table so you don't have to deal with administration and storage challenges with a massive history table.
edited Mar 28 '17 at 18:52
marc_s
7,12053849
answered Jan 25 '16 at 16:37
SQLmojoeSQLmojoe
1,32037
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%2f126402%2fuse-a-sp-to-archive-revision-related-records-in-several-related-tables%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
Creating such a stored procedure is probably going to be complex and error prone. That's why there are temporal databases or temporal features in a database. If you really wanted to do this with a stored procedure, you can have a duplicate schema with a version number column added to all tables.
That way, on each write operation, you can first call the stored procedure which does an INSERT INTO.... SELECT using the same WHERE clause as your write operation. The stored procedure is best initiated by the app which runs the stored procedure before the actual write (UPDATE/DELETE) statement.
If you use triggers, it can be very tricky just figuring out which table(s) to host the trigger and making sure you don't get a trigger storm.
Far easier path is to implement something like Temporal tables in SQL Server 2016: https://msdn.microsoft.com/en-us/library/dn935015.aspx. Takes a bit of work to setup but it's only somewhat tedious work, not very complex work. If you want to keep this history around for a long time, you can even stretch the temporal history table so you don't have to deal with administration and storage challenges with a massive history table.
edited Mar 28 '17 at 18:52
marc_s
7,12053849
answered Jan 25 '16 at 16:37
SQLmojoeSQLmojoe
1,32037
add a comment |
Creating such a stored procedure is probably going to be complex and error prone. That's why there are temporal databases or temporal features in a database. If you really wanted to do this with a stored procedure, you can have a duplicate schema with a version number column added to all tables.
That way, on each write operation, you can first call the stored procedure which does an INSERT INTO.... SELECT using the same WHERE clause as your write operation. The stored procedure is best initiated by the app which runs the stored procedure before the actual write (UPDATE/DELETE) statement.
If you use triggers, it can be very tricky just figuring out which table(s) to host the trigger and making sure you don't get a trigger storm.
Far easier path is to implement something like Temporal tables in SQL Server 2016: https://msdn.microsoft.com/en-us/library/dn935015.aspx. Takes a bit of work to setup but it's only somewhat tedious work, not very complex work. If you want to keep this history around for a long time, you can even stretch the temporal history table so you don't have to deal with administration and storage challenges with a massive history table.
edited Mar 28 '17 at 18:52
marc_s
7,12053849
answered Jan 25 '16 at 16:37
SQLmojoeSQLmojoe
1,32037
add a comment |
Creating such a stored procedure is probably going to be complex and error prone. That's why there are temporal databases or temporal features in a database. If you really wanted to do this with a stored procedure, you can have a duplicate schema with a version number column added to all tables.
That way, on each write operation, you can first call the stored procedure which does an INSERT INTO.... SELECT using the same WHERE clause as your write operation. The stored procedure is best initiated by the app which runs the stored procedure before the actual write (UPDATE/DELETE) statement.
If you use triggers, it can be very tricky just figuring out which table(s) to host the trigger and making sure you don't get a trigger storm.
Far easier path is to implement something like Temporal tables in SQL Server 2016: https://msdn.microsoft.com/en-us/library/dn935015.aspx. Takes a bit of work to setup but it's only somewhat tedious work, not very complex work. If you want to keep this history around for a long time, you can even stretch the temporal history table so you don't have to deal with administration and storage challenges with a massive history table.
edited Mar 28 '17 at 18:52
marc_s
7,12053849
answered Jan 25 '16 at 16:37
SQLmojoeSQLmojoe
1,32037
Creating such a stored procedure is probably going to be complex and error prone. That's why there are temporal databases or temporal features in a database. If you really wanted to do this with a stored procedure, you can have a duplicate schema with a version number column added to all tables.
That way, on each write operation, you can first call the stored procedure which does an INSERT INTO.... SELECT using the same WHERE clause as your write operation. The stored procedure is best initiated by the app which runs the stored procedure before the actual write (UPDATE/DELETE) statement.
If you use triggers, it can be very tricky just figuring out which table(s) to host the trigger and making sure you don't get a trigger storm.
Far easier path is to implement something like Temporal tables in SQL Server 2016: https://msdn.microsoft.com/en-us/library/dn935015.aspx. Takes a bit of work to setup but it's only somewhat tedious work, not very complex work. If you want to keep this history around for a long time, you can even stretch the temporal history table so you don't have to deal with administration and storage challenges with a massive history table.
edited Mar 28 '17 at 18:52
marc_s
7,12053849
answered Jan 25 '16 at 16:37
SQLmojoeSQLmojoe
1,32037
edited Mar 28 '17 at 18:52
marc_s
7,12053849
edited Mar 28 '17 at 18:52
marc_s
7,12053849
edited Mar 28 '17 at 18:52
marc_s
7,12053849
7,12053849
answered Jan 25 '16 at 16:37
SQLmojoeSQLmojoe
1,32037
answered Jan 25 '16 at 16:37
SQLmojoeSQLmojoe
1,32037
answered Jan 25 '16 at 16:37
SQLmojoeSQLmojoe
1,32037
1,32037
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%2f126402%2fuse-a-sp-to-archive-revision-related-records-in-several-related-tables%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
1
depending on the version of sql server you are .. you can look into change data capture or change tracking. That will help you.
– Kin
Jan 15 '16 at 21:25
2
Are you talking about structural changes to your database as in DDL changes? Or are you talking about a user updating a particular row, DML?
– Zane
Jan 15 '16 at 21:41
1
Are you thinking of implementing a temporal database, where each value has a datetime range when it is the effective value, and all past values are also retained?
– Michael Green
Jan 16 '16 at 7:15