Timeline for How can I maintain a SQL schema upgrade that goes out to our users on a regular basis?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 29, 2013 at 14:07 | vote | accept | Michael | ||
| May 28, 2013 at 20:05 | comment | added | Tulains Córdova | Answered: stackoverflow.com/questions/861728/… | |
| May 28, 2013 at 20:02 | history | edited | Michael | CC BY-SA 3.0 |
edited title
|
| May 28, 2013 at 20:01 | comment | added | Michael | @user61852 I apologize for using the reserved keyword "UPDATE" when talking about SQL. Perhaps it would have been better if I said "upgrade" instead (or did I miss your point?) | |
| May 28, 2013 at 19:56 | comment | added | Tulains Córdova | This question doesn't look like an "SQL script update" to me. | |
| May 28, 2013 at 17:28 | comment | added | alroc | If you're using MS SQL Server, SQL Server Data Tools can also help with this problem. | |
| May 28, 2013 at 16:58 | comment | added | Wyatt Barnett | Or if you don't want to pay for redgate, you could use something like RoundHousE to migrate your database. | |
| May 28, 2013 at 16:16 | answer | added | Bobson | timeline score: 7 | |
| May 28, 2013 at 16:00 | comment | added | Dan Pichelman | Are you familiar with Red-Gate's products? It could be that you're reinventing the wheel. | |
| May 28, 2013 at 15:58 | history | asked | Michael | CC BY-SA 3.0 |