Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We are doing distributed development, working at home, office and sometimes at customers.

We are using assembla for source-repository and we need a centralized-remote SQL Server 2008 database hosting for (similar to svn on assembla) our SQL development server.

Can you name / recommend any service providers?

share|improve this question

3 Answers 3

You can try ReliableSite.Net. Get a shared hosting plan with a SQL Server 2008 addon. They allow remote access so you'll be able to develop against it. You'll end up spending under $10/mo for a database up to 1 gb in size.

share|improve this answer

I've used DiscountASP in the past. I had good luck with them and I've heard others have had good luck with them.

I also recommend source control for your SQL server as well. Red Gate has an awesome tool (SQL Source Control) that works with my SVN repository. Great for distributed groups.

share|improve this answer

You don't centralize the database, you add the database source to source control just like any other source. Developers work on their individual SQL Server Developer Edition instances, properly licensed for each individual developer on its workstation. If possible, developer may use the Express Edition on their workstation.

Your project does not contain any database binary file (.MDF, .NDF, .LDF), it only contains .SQL source files that, when run, they deploy the current version of the application schema. Developers never operate on the database with DBA tools, they always operate all changes as .SQL scripts added to the source, modifying the deployment procedure accordingly with the schema changes, and providing for appropriate deployment upgrade. See Version Control and your Database.

share|improve this answer
    
That may or may not work I have a test db of 200gb real data. I have distributing changes here. –  TomTom Nov 8 '10 at 14:51
    
@TomTom: I'm pretty sure those 200Gb are data, not metadata (tables, views, procedures definitions). I'm advocating the scripting of the objects, not the data in those objects (except for data that is metadata). 200Gb of test data can be either generated, it can be bcp-ed in after db generation, or it can even represent the starting v0 of the db. –  Remus Rusanu Nov 8 '10 at 17:23

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.