Deployment method - Backup/restore vs. Batch file?


not sure correct forum, i'll give go.  in process of deploying series of databases development environment production environment.  i've done searching around best practices, haven't found calls out best.   looking find out best approach moving code/tables/views/sp's, dev environment production environment.  due complexity , large number of objects created, backup/restore production server be more prudent creating batch file type thing creates objects through series of scripts? 

 

 

 n. edmonds wrote:

  due complexity , large number of objects created, backup/restore production server be more prudent creating batch file type thing creates objects through series of scripts?  

 scripts best practice since can backup/restore (no matter how tempting) only 1 time, @ beginning. once have data in production database have scripts, time used process.

scripts have advantage: can save them, modify them , rerun them.

 related article quote: "as start may easier manually check specific business or data conditions, build scripts on time work towards assembling them automated process."

http://www.mssqltips.com/sqlservertip/1240/sql-server-dba-checklist/





SQL Server  >  Getting started with SQL Server



Comments

Popular posts from this blog

Conditional formatting a graph vertical axis in SSRS 2012 charts

Register with Power BI failed

SQL server replication error Cannot find the dbo or user defined function........