DDT is used to update database anywhere in you dev environment. Having the DDT structures on the central SQL Server will give access to all developers, and then they can deploy the database on their own machine if you want. But the DDT structure would be changed directly on the central SQL Server. No matter what version the target database is, DDT will take care of it and bring it to the current.

So if I understand correctly, the scenario for a single database app would work like this:

1. Each dev has a local SQL instance with a copy of the database, and on a server there's another copy of the database.

2. The central database is where any/all changes are made, as well as source code check-ins/outs.

3. DDT is used to update the local dev databases.

Is that correct? Do you have any posts on how to properly source control the SQL databases and DDT?

(Yes, I'm a StrataFrame newbie, thanks for the remedial help)

Hi William.

Welcome to the community!

Follow this post and it will give you a hint:

http://forum.strataframe.net/FindPost28750.aspx

Hello,

We're ready to start installing our StrataFrame software in a team environment and I'm looking for documentation on how best to do so. We use VS2010, SQL Server Express 2008 R2, and Team Foundation Server 2008 (planning to upgrade to TFS2010 soon).

Each developer will have a local SQL Express instance, and we'll have a central SQL instance for testing of builds and deployment scenarios.

I'm also interested in documentation on how the DDT can be used to deploy (propagate?) local SQL schema changes to the other developers in the team via TFS source control. In our Visual FoxPro projects, we use the StoneField Database Toolkit to send updates

Any suggestions would be appreciated.

Thanks.