Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
muralidaran_r
Starting Member
13 Posts |
 Posted - 2008-08-05 : 00:59:03
|
| We have developed a database which acts as a back end to .net applicationWe have to distribute this database with sql server installation in DVD to customers.How to do this?In future many customers will expect changes in thier database. How to update patches without affecting customers data?how to maintain Database versions for each and every customers successfully?If any thing stops working for a customer after new patch/update how to rollback to previous working version?Please explain in detail. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-08-05 : 01:04:18
|
| Get the database exactly how you want it, detach it, then add the MDF/LDF files to DVD. The customer can then attach them using those files. Patches may affect customers, depends if there are schema changes. You'll probably need downtime for schema changes.You'll need source control software for this.You'll need to write scripts that undo's your changes.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
 |
|
|
muralidaran_r
Starting Member
13 Posts |
Posted - 2008-08-05 : 01:35:35
|
| I also want to prevent access to MDF/LDF files. |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-08-06 : 23:35:05
|
| You can't access db files while sql is running, but you are unable to stop admins. They can stop sql and do whatever they like. |
|
|
|
|
|
|
Database Deployment and Maintenance & Versions