Coming from the world of Lan-based databases, I'm curious as to what other developers are doing about this. When your client is keeping all their data on an ISP's SQL Server (often inevitably chosen on your own recommendation), there is always the worry that your client will fall out with the ISP and their data may become inaccessible, or the ISP may simply disappear. The general worry being that my client no longer has total control over their own data.
I was thinking of running Microsoft's Database Publishing Wizard from a command line as a Windows Service which my client would run locally - then it occurred to me that I'm losing a lot of the benefit (to me) of an Asp.Net solution which means I can maintain the client's entire system without going near their physical site.
Then I thought that perhaps I could run the Database Publishing Wizard at the server end, and e-mail the resultant .sql text file to the client. I don't h ...
Go to the complete details ...