October 21, 2014 at 1:12 pm
Hi Techies,
I'm SW developer and using the MSSQL in the current project.
At this moment we have a problem with releases of our scripts because we don't have a process to manage the scripts by each release.
For example:
- in the first release we delivered the schema, procedures, functions and configuration data.
- In the second release we changed a table and added a new column... in this release we just handed instructions for the alter table and other scripts to update this column with a default value.
When/If the team decides to install the database in another environment it should be created a package with all object including most recent changes.
Does anybody have any idea/suggestion/tool/process that can share with us please?
Best Regards,
Xavy
October 21, 2014 at 2:45 pm
You could script up the 'alter table' update!
October 21, 2014 at 9:14 pm
Yes... right click on the database in SSMS and click on [Tasks], [Generate Scrips], and then follow your nose. Of course, that just to get you out of the woods. What you really need to do is start treading database code as actual code and start using source control on it.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 22, 2014 at 1:14 am
Put your database code into source control and start treating it, as much as possible, like your application code. But, if you really want to start talking about database deployment and mechanisms around it, I strongly recommend starting here.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply