<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.infopathdev.com:443/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Automating DBXL tasks with the DBXL Migration Tool</title><link>https://www.infopathdev.com:443/blogs/david/archive/2007/08/30/automating-dbxl-tasks-with-the-dbxl-migration-tool.aspx</link><description>Two commonly requested features for Qdabra DBXL are automatically populating the database and migrating content from one site to another. We have developed a tool that allows you to do both. The DBXL Document Deployer is an XML-driven, command-line tool</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP3 (Build: 31118.962)</generator><item><title>How to migrate complex solutions using the Migration Tool - David Airapetyan</title><link>https://www.infopathdev.com:443/blogs/david/archive/2007/08/30/automating-dbxl-tasks-with-the-dbxl-migration-tool.aspx#30554</link><pubDate>Thu, 17 Jul 2008 19:44:01 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:30554</guid><dc:creator>How to migrate complex solutions using the Migration Tool - David Airapetyan</dc:creator><description>&lt;p&gt;Pingback from &amp;nbsp;How to migrate complex solutions using the Migration Tool - David Airapetyan&lt;/p&gt;
&lt;img src="https://www.infopathdev.com:443/aggbug.aspx?PostID=30554" width="1" height="1"&gt;</description></item><item><title>re: Automating DBXL tasks with the DBXL Migration Tool</title><link>https://www.infopathdev.com:443/blogs/david/archive/2007/08/30/automating-dbxl-tasks-with-the-dbxl-migration-tool.aspx#22931</link><pubDate>Sun, 09 Sep 2007 19:05:27 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:22931</guid><dc:creator>Patrick Halstead</dc:creator><description>&lt;p&gt;This is a great tool for auto-populating test sites or taking backups of existing sites. You can also migrate solutions from one site to another. Check out David's post on how to do migration: &lt;a rel="nofollow" target="_new" href="http://www.infopathdev.com/blogs/david/archive/2007/09/06/how-to-migrate-complex-solutions-using-the-migration-tool.aspx"&gt;www.infopathdev.com/.../how-to-migrate-complex-solutions-using-the-migration-tool.aspx&lt;/a&gt;.&lt;/p&gt;
&lt;img src="https://www.infopathdev.com:443/aggbug.aspx?PostID=22931" width="1" height="1"&gt;</description></item><item><title>re: Automating DBXL tasks with the DBXL Migration Tool</title><link>https://www.infopathdev.com:443/blogs/david/archive/2007/08/30/automating-dbxl-tasks-with-the-dbxl-migration-tool.aspx#22893</link><pubDate>Thu, 06 Sep 2007 04:47:14 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:22893</guid><dc:creator>davidair</dc:creator><description>&lt;p&gt;Addendum: it turns out that DocumentDeployer will also run against a DBXL 2.0 instance. However, you need to make sure that you do not use the new DB aliases such as #DBXLDB# (sample XML files make use of it to keep the examples generic). Instead, you will have to replace #DBXLDB# with the actual database name.&lt;/p&gt;
&lt;img src="https://www.infopathdev.com:443/aggbug.aspx?PostID=22893" width="1" height="1"&gt;</description></item></channel></rss>