- Still, I find the Database Project useful not only as a source repository of migration scripts, but also:
- The list of Database References helps keep the 3 environments handy when wanting to apply a script to any particular environment.
- And, when you right-click a database object in the Server Explorer and click Generate Create Script to Project = very handy.
Sent: Thursday, 22 May 2008 4:03 p.m.
Subject: [dotnet] RE: visual studio database projects in 2005 or 2008 -->
Sent: Thursday, 22 May 2008 3:51 p.m.
Subject: [dotnet] RE: visual studio database projects in 2005 or 2008
- Each week I create a new migration script e.g. Update20080523.sql.
- All database changes made to DEV, are scripted and saved to this file.
- I test and re-test it in DEV. Obviously this requires some smarts around whether to attempt to recreate objects or update data (IF EXISTS…).
- I apply it to TEST, usually only once.
- Finally, during Friday’s change window, I apply it to PROD; definitely only once.
- It helps to place a comment at the top of the file referencing the changed objects.
Sent: Thursday, 22 May 2008 3:31 p.m.
Subject: [dotnet] visual studio database projects in 2005 or 2008 -->
Other related posts:
That Awkward Moment
Geek Post Monthly Newsletter Volume 2 Issue 9
Geek Post Monthly Newsletter Volume 2 Issue 8
Add a comment
Please note: comments that are inappropriate or promotional in nature will be deleted.
E-mail addresses are not displayed, but you must enter a valid e-mail address to confirm your comments.
Are you a registered Geekzone user? Login to have the fields below automatically filled in for you and to enable links in comments. If you have (or qualify to have) a Geekzone Blog then your comment will be automatically confirmed and shown in this blog post.