SQl Server Installation of Additions/Modifications
We're moving forward with our first installation of application with a SQL Server backend. The front end is in MS Access 2013.
At some point in the not too distant future we'll move into production. We'll load the startup DB by restoring it to the production SQL Server.
In all likelyhood we'll almost immediately be making revisions to the SQL DB. Up to the point of production we've been going into the test DB to make and test changes. What will the process be when we move to production?
We'll have a test SQL DB where we can make changes but how do we move them to production. Examples of changes I'm thinking of are New table field
New Table
New View
Remove Field From Table
Revise a View
New Stored Procedure
Revise Existing Stored Procedure
Having made and tested these revisions in the test DB how will each of these revisions be moved from the Test DB to production?
At some point in the not too distant future we'll move into production. We'll load the startup DB by restoring it to the production SQL Server.
In all likelyhood we'll almost immediately be making revisions to the SQL DB. Up to the point of production we've been going into the test DB to make and test changes. What will the process be when we move to production?
We'll have a test SQL DB where we can make changes but how do we move them to production. Examples of changes I'm thinking of are New table field
New Table
New View
Remove Field From Table
Revise a View
New Stored Procedure
Revise Existing Stored Procedure
Having made and tested these revisions in the test DB how will each of these revisions be moved from the Test DB to production?
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Microsoft Access
Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.
226K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
I think both approaches are needed. Create scripts as needed, especially for converting data, then double check your work with a comparison. Also, make sure that all deployments are done to Test first using only scripts, with no manual intervention, before they are applied to Production. That's why I said that running the scripts is actually part of the testing process.
Cheers,
Armen