StrataFrame Forum » StrataFrame Database Deployment Toolkit » Database Deployment Toolkit (How do I?) » Deployment Errors

Deployment Errors

Aaron Young — Wed, 03 Sep 2008 16:58:17 GMT

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 ? :)

Aaron

RE: Deployment Errors

Aaron Young — Wed, 03 Sep 2008 16:58:17 GMT

Oops - got it. My default values for the ROWGUID fields have become corrupt somehow. They should be "newsequentialid()" but somehow they are now "(newsequentialid()".

RE: Deployment Errors

Aaron Young — Wed, 03 Sep 2008 15:24:58 GMT

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

RE: Deployment Errors

Aaron Young — Tue, 02 Sep 2008 16:21:46 GMT

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

RE: Deployment Errors

Dustin Taylor — Tue, 02 Sep 2008 09:58:34 GMT

You do have SMO objects loaded on your new SQL server, correct?