I've having a problem where my .Install script works manuall when I replace {ObjectQualifier} and {Databaseowner} with "", but not in the module installation. I'm getting errors that lead me to beleive the search / replace that DNN is doing isn't what I understand. I have a table like this:

IF OBJECT_ID(N'{DatabaseOwner}[{ObjectQualifer}Interface]') IS NULL
BEGIN
    CREATE TABLE {DatabaseOwner}[{ObjectQualifer}Interface] (
  [PortalId] INT NOT NULL ,
  [InterfaceId] INT IDENTITY (1, 1) NOT NULL ,
  [ComponentId] INT NOT NULL ,
  [InterfaceTypeId] INT NOT NULL ,
  [InternalName] NCHAR(10) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
  [ExternalLabel] NCHAR(10) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
  [GUID] NCHAR(10) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
  [Comment] NVARCHAR(50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
  [ConnectionId] INT NULL ,
  [Version] TIMESTAMP NULL
    ) ON [PRIMARY]
END

EXEC dbo.sp_addextendedproperty N'MS_Description', N'Portal identifier', N'user', N'{DatabaseOwner}', N'TABLE', N'{ObjectQualifier}Interface', N'COLUMN', N'PortalId'
EXEC dbo.sp_addextendedproperty N'MS_Description', N'Unique interface identifier', N'user', N'{DatabaseOwner}', N'TABLE', N'{ObjectQualifier}Interface', N'COLUMN', N'InterfaceId'
EXEC dbo.sp_addextendedproperty N'MS_Description', N'Component identifier', N'user', N'{DatabaseOwner}', N'TABLE', N'{ObjectQualifier}Interface', N'COLUMN', N'ComponentId'
EXEC dbo.sp_addextendedproperty N'MS_Description', N'Interface type', N'user', N'{DatabaseOwner}', N'TABLE', N'{ObjectQualifier}Interface', N'COLUMN', N'InterfaceTypeId'
EXEC dbo.sp_addextendedproperty N'MS_Description', N'Internal name for interface', N'user', N'{DatabaseOwner}', N'TABLE', N'{ObjectQualifier}Interface', N'COLUMN', N'InternalName'
EXEC dbo.sp_addextendedproperty N'MS_Description', N'Eternal label for interface', N'user', N'{DatabaseOwner}', N'TABLE', N'{ObjectQualifier}Interface', N'COLUMN', N'ExternalLabel'
EXEC dbo.sp_addextendedproperty N'MS_Description', N'GUID or MAC for interface', N'user', N'{DatabaseOwner}', N'TABLE', N'{ObjectQualifier}Interface', N'COLUMN', N'GUID'
EXEC dbo.sp_addextendedproperty N'MS_Description', N'Interface identifier of remote connection', N'user', N'{DatabaseOwner}', N'TABLE', N'{ObjectQualifier}Interface', N'COLUMN', N'ConnectionId'
EXEC dbo.sp_addextendedproperty N'MS_Description', N'Version timestamp for concurrency control', N'user', N'{DatabaseOwner}', N'TABLE', N'{ObjectQualifier}Interface', N'COLUMN', N'Version'
GO

It's looking to me like the N'*** items are not being translated. If there a good reference for the proper guidelines for converting a SQL Management Studio script that includes foriegn keys and extended attributes to somethign the DNN will install properly?

The settings are defaults. The isntallation is into a virgin DNN installation I use for a test bed. In this case I would expect the database owner to end up being either blank or dbo and the object qualifier is nothing (blank). Items with outextended properties work fine.

For example the normal table creates would look like this:

CREATE TABLE [dbo].[Instance](
    [PortalId] [int] NOT NULL CONSTRAINT [DF_Instance_PortalId]  DEFAULT ((0)),
-edited  for brevity-
    [Version] [timestamp] NOT NULL,
 CONSTRAINT [PK_Instance] PRIMARY KEY NONCLUSTERED
(
    [InstanceId] ASC
)WITH (PAD_INDEX  = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]

GO
EXEC sys.sp_addextendedproperty @name=N'MS_Description', @value=N'Portal identifier' , @level0type=N'SCHEMA',@level0name=N'dbo', @level1type=N'TABLE',@level1name=N'Instance', @level2type=N'COLUMN',@level2name=N'PortalId'
GO
 

The issue I need some clarity on is the proper "DNN" way of making those work with a standard module isntallation and the dbo and oq tags. For example if I was going to use an object qualifier of CPM I would expect the create to llok like this:

CREATE TABLE [dbo].[CPMInstance](
    [PortalId] [int] NOT NULL CONSTRAINT [DF_CPMInstance_PortalId]  DEFAULT ((0)),
-edited  for brevity-
    [Version] [timestamp] NOT NULL,
 CONSTRAINT [PK_CPMInstance] PRIMARY KEY NONCLUSTERED
(
    [InstanceId] ASC
)WITH (PAD_INDEX  = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]

GO
EXEC sys.sp_addextendedproperty @name=N'MS_Description', @value=N'Portal identifier' , @level0type=N'SCHEMA',@level0name=N'dbo', @level1type=N'TABLE',@level1name=N'CPMInstance', @level2type=N'COLUMN',@level2name=N'PortalId'
GO

Since today I don't need an object qualifier, changing the {DatabaseOwner} and {ObjectQualifier} to spaces or simply not using the tags at all in the SQL works. I can't count on that long term, but don't see any examples in the modules I've reviewed that take into account the circumstances I've noted above taht show me how to it properly.