﻿<?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  » Updating table with identity field</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 10:13:00 GMT</lastBuildDate><ttl>20</ttl><item><title>Updating table with identity field</title><link>http://forum.strataframe.net/FindPost8589.aspx</link><description>Hi,&lt;/P&gt;&lt;P&gt;In the process of migrating my database update systeem to the strataframe system, i've made several definition errors. A few of them were PK fields with identity specification where there should not be a identity specification. So i made the corrections in the DDT and generated a new deployment package. When i applied the package&amp;nbsp;to my test server i found out that the identity specification stills exsist!!! Is this a bug or do i do something wrong?</description><pubDate>Mon, 30 Apr 2007 16:13:04 GMT</pubDate><dc:creator>softaca</dc:creator></item><item><title>RE: Updating table with identity field</title><link>http://forum.strataframe.net/FindPost8592.aspx</link><description>We are hoping to have it included in&amp;nbsp;the 1.6.1 update.&amp;nbsp;</description><pubDate>Mon, 30 Apr 2007 16:13:04 GMT</pubDate><dc:creator>Trent L. Taylor</dc:creator></item><item><title>RE: Updating table with identity field</title><link>http://forum.strataframe.net/FindPost8591.aspx</link><description>Thanks for the very quick reply. I already applied the workaround as you mentioned but thought to mention it anyhow, because if this happended in a life situation the problem would have been bigger. Any idea when the fix will be available?</description><pubDate>Mon, 30 Apr 2007 15:49:55 GMT</pubDate><dc:creator>softaca</dc:creator></item><item><title>RE: Updating table with identity field</title><link>http://forum.strataframe.net/FindPost8590.aspx</link><description>This is already a known issue and is slated to be in the next update.&amp;nbsp; The problem is that you are trying to make an existing field have an identity after it has already been created.&amp;nbsp; If the table was deployed clean the first time it would work.&amp;nbsp; This is already known and a fix is in the works.&amp;nbsp; To work around, you can open up the SQL Management Studio and set the identity on the database that already exists.</description><pubDate>Mon, 30 Apr 2007 15:44:33 GMT</pubDate><dc:creator>Trent L. Taylor</dc:creator></item></channel></rss>