﻿<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>StrataFrame Forum » StrataFrame Database Deployment Toolkit » Database Deployment Toolkit (How do I?)  » DDT question...</title><generator>InstantForum 2017-1 Final</generator><description>StrataFrame Forum</description><link>http://forum.strataframe.net/</link><webMaster>StrataFrame Forum</webMaster><lastBuildDate>Mon, 08 Jun 2026 23:30:35 GMT</lastBuildDate><ttl>20</ttl><item><title>DDT question...</title><link>http://forum.strataframe.net/FindPost9237.aspx</link><description>The database deployment toolkit isn't intended to be visual source safe for databases, right?</description><pubDate>Fri, 01 Jun 2007 08:30:48 GMT</pubDate><dc:creator>StarkMike</dc:creator></item><item><title>RE: DDT question...</title><link>http://forum.strataframe.net/FindPost9240.aspx</link><description>No.&amp;nbsp; It can be used this way if you have a package file that is exported you could then re-import it back to the state of the exported file.&amp;nbsp; But the DDT is designed to be a database design and implementation tool.&amp;nbsp; There are many benefits past this, such as creating psuedo table structures that are not deployed but allow your BOs to be mapped to these schemas for strong-typing and then use XML as the data source, for example.&amp;nbsp; &lt;/P&gt;&lt;P&gt;When using the DDT in a normal sense, it will also create all of the SPROCS for INSERTs, UPDATEs, and DELETEs that also support concurrency just by clicking a check box.&amp;nbsp; These SPROCs tie into the BOs by just setting the CRUD SPROC properties to True.&amp;nbsp; There is much more than this, but its design and purpose is not to be a source safe for databases.</description><pubDate>Fri, 01 Jun 2007 08:30:48 GMT</pubDate><dc:creator>Trent L. Taylor</dc:creator></item></channel></rss>