Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
achiribo
Starting Member
3 Posts |
Posted - 2007-02-27 : 10:46:42
|
Is there a way to find out when a stored procedure (or a view or any other object) was last updated? I know how to find the creation date, but often we need to find out the updated date, for example, to confirm what items have changed in a development environment so they can be moved to production. Any ideas or suggestions would be greatly appreciated.Thanks! |
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2007-02-27 : 11:55:21
|
1. No.2. Use a source-safe process to control objects changes/migrations to production.see best practices on this issue detailed by other members on this site....nr, tkizer, kristen, robvolk, merkin, etc... |
|
|
Kristen
Test
22859 Posts |
Posted - 2007-02-27 : 12:31:27
|
An Andrew has said.I strongly recommend that you store the "Source Code" for your objects in separate files, and manage that with Version Control - rather than just changing things in the database directly.A half-way-house would be to script the whole database, e.g. each night, and then put that script through the Version Control system.jezemine has a tool that will do that, I believe.However, there are database comparison tools which can script the differences between two databases - e.g. your Version1 database and the newer Version2 database; you could then use that as the basis for a release script.RedGate have such a tool, but I expect there are others.Kristen |
|
|
achiribo
Starting Member
3 Posts |
Posted - 2007-02-27 : 13:37:01
|
That's what I thought the answer would be. Source control will be for us, then. Thanks for the quick replies. |
|
|
Kristen
Test
22859 Posts |
|
achiribo
Starting Member
3 Posts |
Posted - 2007-02-28 : 10:51:34
|
Thanks a lot for the very informative post, Kristen! I have bookmarked it. |
|
|
|
|
|
|
|