Deployment Errors


Author
Message
Aaron Young
Aaron Young
StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)
Group: StrataFrame Users
Posts: 277, Visits: 1.1K
Hi,

I haven't run a deployment on my development machine for sometime. However, the last time I did there were no problems and the model hasn't changed much since then. I have tried deploying to a new SQL database and every table throws up a similar error (see attached screenshot). I have tried this with the latest beta install and it does the same thing.

The deployment does create a new empty database but no tables are added.

Have I missed something silly as it wouldn't be the first time ? Smile

Aaron

Attachments
Error.png (168 views, 34.00 KB)
Dustin Taylor
Dustin Taylor
StrataFrame Team Member (664 reputation)
Group: StrataFrame Users
Posts: 364, Visits: 771
You do have SMO objects loaded on your new SQL server, correct?
Aaron Young
Aaron Young
StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)
Group: StrataFrame Users
Posts: 277, Visits: 1.1K
Hi Dustin,

I am not using a new SQL Server - it is the same development system I have always used and SMO hasn't been uninstalled since the last time I used DDT.

Thanks anyway,

Aaron

Aaron Young
Aaron Young
StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)
Group: StrataFrame Users
Posts: 277, Visits: 1.1K
I have found the SQL statement which is causing the problem. When the DDT tries to create a table, it generates code such as:-

CREATE TABLE [dbo].[BIN](
 [ID] [int] NOT NULL CONSTRAINT [DF_BIN_ID]  DEFAULT (0),
 [DEPOT] [int] NULL CONSTRAINT [DF_BIN_DEPOT]  DEFAULT (0),
 [NAME] [varchar](40) NULL CONSTRAINT [DF_BIN_NAME]  DEFAULT (''),
 [INACTIVE] [bit] NULL CONSTRAINT [DF_BIN_INACTIVE]  DEFAULT (0),
 [ROWGUID] [uniqueidentifier] NOT NULL CONSTRAINT [DF_BIN_ROWGUID]  DEFAULT (newsequentialid()
) ON [PRIMARY]

It is the "ON [PRIMARY]" which is causing the error. I have not changed anything in File Groups and the model did work before with earlier DDT versions. Have I missed something stupid?

Aaron


Aaron Young
Aaron Young
StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)StrataFrame User (439 reputation)
Group: StrataFrame Users
Posts: 277, Visits: 1.1K
Oops - got it. My default values for the ROWGUID fields have become corrupt somehow. They should be "newsequentialid()" but somehow they are now "(newsequentialid()".

Smile

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search