﻿<?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 » Issues  » DDT Exceptions when deploying package.</title><generator>InstantForum 2017-1 Final</generator><description>StrataFrame Forum</description><link>http://forum.strataframe.net/</link><webMaster>StrataFrame Forum</webMaster><lastBuildDate>Tue, 09 Jun 2026 06:06:09 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: DDT Exceptions when deploying package.</title><link>http://forum.strataframe.net/FindPost18599.aspx</link><description>Hi Charles!&lt;P&gt;Hope everything is fine with you.&lt;/P&gt;&lt;P&gt;You might consider using row version instead... &lt;/P&gt;&lt;P&gt;&lt;A href="http://forum.strataframe.net/FindPost16196.aspx"&gt;http://forum.strataframe.net/FindPost16196.aspx&lt;/A&gt;</description><pubDate>Tue, 19 Aug 2008 16:38:41 GMT</pubDate><dc:creator>Ivan George Borges</dc:creator></item><item><title>DDT Exceptions when deploying package.</title><link>http://forum.strataframe.net/FindPost16718.aspx</link><description>Hi, &lt;/P&gt;&lt;P&gt;I have added a new Data Deployment package in my DDT project and I get a few exceptions:&lt;/P&gt;&lt;P&gt;1. When deploying a uniqueidentifier column that contains NULL values, I get an Invalid Cast exception. After filling up all values it works fine. &lt;/P&gt;&lt;P&gt;2. When deploying a nvarchar column that contains NULL values, I get an exception saying that it cannot convert DBNull to String. After filling the values&amp;nbsp;here too, it works fine.&lt;/P&gt;&lt;P&gt;3. When deploying a timestamp column, I get an SQL exception saying that timestamp columns cannot be assigned. Which is true, since timestamps get values on their own. &lt;/P&gt;&lt;P&gt;I can provide you with the package if you think it could help more.</description><pubDate>Tue, 19 Aug 2008 16:38:41 GMT</pubDate><dc:creator>George Nentidis</dc:creator></item><item><title>RE: DDT Exceptions when deploying package.</title><link>http://forum.strataframe.net/FindPost18598.aspx</link><description>Sorry - I really was being thick.  &lt;br&gt;
&lt;br&gt;
:blush:&lt;br&gt;
&lt;br&gt;
I read http://forum.strataframe.net/FindPost10529.aspx - Ben's reply over a year ago saying you had to set the combobox at the bottom of the Table Properties to the field used for rowversioning and I looked at that combo and set it to the pk ....&lt;br&gt;
&lt;br&gt;
Slowly it is starting to gel ... slowly&lt;br&gt;
&lt;br&gt;
SET OPTIMISTIC TIMESTAMP&lt;br&gt;
SET THE ROWVERSION COMBO TO THE TIMESTAMP FIELD  :w00t:&lt;br&gt;
&lt;br&gt;
&lt;br&gt;</description><pubDate>Tue, 19 Aug 2008 16:34:16 GMT</pubDate><dc:creator>Charles R Hankey</dc:creator></item><item><title>RE: DDT Exceptions when deploying package.</title><link>http://forum.strataframe.net/FindPost18597.aspx</link><description>&lt;br&gt;
I am working with DDT right now trying to get a more granular understanding of how to make it do its tricks.  &lt;br&gt;
&lt;br&gt;
I am trying to create a database from scratch in DDT, then deploy to server.&lt;br&gt;
&lt;br&gt;
This is the first time I've tried having DDT create CRUD sprocs.&lt;br&gt;
&lt;br&gt;
Table definition includes a timestamp&lt;br&gt;
&lt;br&gt;
I have the update and delete sproc marked as optimistic timestamp&lt;br&gt;
&lt;br&gt;
Deployment fails on creating update sproc saying you can't update a timestamp&lt;br&gt;
Insert sproc fails saying use a field list and exclude timestamp or enter a default (not sure what works as a default for a timestamp - 0 and ' ' don't seem to.)&lt;br&gt;
&lt;br&gt;
I see no way to influence how sprocs are going to be generated.&lt;br&gt;
&lt;br&gt;
From previous messages in this thread I'm thinking maybe DDT doesn't handle sproc creation when there are timestamps.  I tried deleting timestamp field, deploying, then adding timestamp, unchecking autogenerate sprocs and deploying again - of course that wiped out my crud sprocs as they had been initially creaeted by DDT and had the extended props.&lt;br&gt;
&lt;br&gt;
Soooo - how do you have DDT generate sprocs that use Optimistic timestamp for update?&lt;br&gt;
&lt;br&gt;
Sorry if I'm just being boneheaded but searched forum and don't really see an answer (or at least one that is simple enough for me to understand :)&lt;br&gt;
&lt;br&gt;</description><pubDate>Tue, 19 Aug 2008 16:13:34 GMT</pubDate><dc:creator>Charles R Hankey</dc:creator></item><item><title>RE: DDT Exceptions when deploying package.</title><link>http://forum.strataframe.net/FindPost16721.aspx</link><description>[quote]When deploying a uniqueidentifier column that contains NULL values, I get an Invalid Cast exception. After filling up all values it works fine. [/quote]&lt;/P&gt;&lt;P&gt;The answer to this is already out here on the forum as I have answered this a number of times already...you cannot have NULL data in a deployment data package.&amp;nbsp; We may make a change in the future to allow this...but it will require a relatively large change in the way teh data is packaged...and then making it backward compatible, etc.&lt;/P&gt;&lt;P&gt;[quote] When deploying a nvarchar column that contains NULL values, I get an exception saying that it cannot convert DBNull to String. After filling the values&amp;nbsp;here too, it works fine.[/quote]&lt;/P&gt;&lt;P&gt;Read the first answer.&lt;/P&gt;&lt;P&gt;[quote]When deploying a timestamp column, I get an SQL exception saying that timestamp columns cannot be assigned. Which is true, since timestamps get values on their own. [/quote]&lt;/P&gt;&lt;P&gt;First time I have ever heard of someone trying to deploy a timestamp value since this is generated by the SQL side...I can add this to the list to look at so ensure that a timestamp column never tries to deploy data.&amp;nbsp; I will put this on the list, but we are in the middle of making a lot of changes to the DDT anyway, so this will not be an immediate change.&lt;/P&gt;&lt;P&gt;[quote]I can provide you with the package if you think it could help more. [/quote]&lt;/P&gt;&lt;P&gt;Not necessary....the top 2 problems will not be changed (at least in the immediate future).&amp;nbsp; I will look at the time stamp deployment next week.</description><pubDate>Fri, 30 May 2008 09:39:07 GMT</pubDate><dc:creator>Trent L. Taylor</dc:creator></item></channel></rss>