Timeline for How to retain the current value of a sequence when copying a database in SQL Server
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 30, 2019 at 23:19 | answer | added | Tahir Riaz | timeline score: 2 | |
| Jun 30, 2019 at 18:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Apr 17, 2019 at 18:01 | history | tweeted | twitter.com/StackDBAs/status/1118575140118441984 | ||
| Mar 2, 2019 at 12:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Apr 6, 2018 at 18:07 | answer | added | Diane | timeline score: 0 | |
| Apr 6, 2018 at 8:16 | comment | added | Xlayman | Yes, I know how to reset the sequence to a desired value. I was just wondering if it's possible to retain the sequence's current value in the copy process (which would be the easiest way to maintain integrity between table and sequence), or is the only way to write a script that checks the currently highest primary key from related table and the resets the sequence according to that. | |
| Apr 6, 2018 at 2:59 | history | edited | MDCCL | CC BY-SA 3.0 |
Reworded title.
|
| Apr 6, 2018 at 2:26 | comment | added | Sean Gallardy |
Not using the copy database method, though it shouldn't be too hard to use alter sequence in your scripts to reset the value: learn.microsoft.com/en-us/sql/t-sql/statements/…
|
|
| Apr 5, 2018 at 23:17 | history | edited | Joe Obbish |
adjusting tags
|
|
| Apr 5, 2018 at 21:26 | review | First posts | |||
| Apr 5, 2018 at 22:14 | |||||
| Apr 5, 2018 at 21:24 | history | asked | Xlayman | CC BY-SA 3.0 |