By Paul Chase - 10/30/2007
I get the following error whenver I try to save a record in the DDT. any Ideas? 
|
By Trent L. Taylor - 10/30/2007
This indicates that the index field had a record that was added that did not have a parent record. This could be due to a failed INSERT or DELETE from a previous record. This is a SQL Server message indicating that the foreign key relationship was not maintained. This should not happen anywhere within the DDT, can you give more specifics? Also, does this happen on every table and every profile or just a specific table or index that youa re trying to save. It would be my guess that the primary key index (which we create dynamically upon the save) may have been removed and previously existed or something of that nature. Any details would be appreciated. Thanks. 
|
By Paul Chase - 10/30/2007
Trent,It appears to be an issue with Guid Prime keys where ROWGUID is set to true. I'm still checking it out but that looks like what is causing it
|
By StrataFrame Team - 10/31/2007
Paul, could you backup your StrataFrame database and email me the *.bak file. This looks like the same error that Jason Seidell is getting, and he's supposed to be sending me his StrataFrame.bak file, too, but I won't know for sure until I can look at it with the data.
|
By Paul Chase - 11/1/2007
Ben,What is you Email address?
|
By Trent L. Taylor - 11/1/2007
Paul, I sent you a PM with the information. Thanks.
|
By StrataFrame Team - 11/5/2007
OK, Paul, we tracked down the problem. The primary key could not be re-created because there is already an index on those tables that is named the same as the primary key that the DDT is trying to recreate. So, we fixed the problem by deleting the index under the table that was PK_[TableName] where the index was not a primary index (if it's the blue rolodex icon, not the yellow key icon). Once you delete the index, modify the structure of the table and save it and the index will be recreated.Let me know it works out for you.
|
By Paul Chase - 11/6/2007
thanks Ben I'll look at it
|
By Paul Chase - 11/7/2007
Ben,Here is the problem, I have tables that have the following A GUID PrimeKey that is also a rowguid specification for replication and a default value of newsequentialid. When the table is imported into DDT it loses its rowguid specification so when it is re-exported it is all messed up, below is a create table script that will create a table with the attributes I mentioned. If you create that table and import -export with the DDT you will see what I mean. /****** Object: Table [dbo].[Contacts] Script Date: 11/07/2007 11:12:43 ******/ SET ANSI_NULLS ONGO SET QUOTED_IDENTIFIER ONGO SET ANSI_PADDING ONGO CREATE TABLE [dbo].[Contactsx]([CON_PK] [uniqueidentifier] ROWGUIDCOL NOT NULL DEFAULT (newsequentialid()),[Con_FK_ID] [uniqueidentifier] NOT NULL,[CON_TABLE] [nvarchar] (25) NOT NULL,[CON_ContactType] [nchar] (30) NOT NULL,[CON_Title] [varchar] (10) NOT NULL,[CON_FirstName] [varchar] (20) NOT NULL,[CON_MiddleName] [varchar] (20) NOT NULL,[CON_LastName] [varchar] (50) NOT NULL,[Con_Name] [varchar] (60) NOT NULL,[CON_Suffix] [varchar] (50) NOT NULL,[CON_Phone] [char] (14) NOT NULL,[CON_CellPhone] [char] (14) NOT NULL,[CON_FaxPhone] [char] (14) NOT NULL,[CON_TollFree] [char] (14) NOT NULL,[CON_PhoneExt] [char] (4) NOT NULL,[CON_TollFreeExt] [char] (4) NOT NULL,[CON_EmailAddress] [char] (60) NOT NULL,[CON_Birthday] [datetime] NOT NULL,[CON_Anniversary] [datetime] NOT NULL,[CON_SpouseName] [char] (60) NOT NULL,[CON_JobTitle] [char] (30) NOT NULL,[CON_ManagersName] [char] (40) NOT NULL,[CON_AssistantsName] [char] (40) NOT NULL,[LOCNCODE] [varchar] (12) NOT NULL,[CREATDDT] [datetime] NOT NULL,[MODIFDT] [datetime] NOT NULL,CONSTRAINT [PK_Contactsx] PRIMARY KEY CLUSTERED ( [CON_PK] ASC) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]) ON [PRIMARY]
|
By StrataFrame Team - 11/8/2007
Yes, we currently don't have the ability to store the RowGuid option for a field, and for some reason the primary key index is not being set as primary when the table is imported, so I'll have to look into both of those. It might be a couple days before I can get you a fix, though.
|
By Paul Chase - 11/8/2007
Ben,I am in no hurry for it I still do all my changes etc on SQL and as it is a replicated DB structure changes are handled there. I Just wanted to make sure you knew what was causing the issue. Paul
|
|