When I performed the DNN upgrade from 3.0.12 to 3.0.13, the upgrade errored out.  Even though the code I dropped on top of my install runs fine (haven't tested everything though), the database script did not run correctly it seems.

I ran it manually, and this is the first error in the script:

The constraint 'PK_Users' is being referenced by table 'DnnForge_NewsArticles_Article', foreign key constraint 'FK_DnnForge_NewsArticles_Article_Users'.

Therefore, a few errors following in the script. 

I'm going to try and figure out what needs to be added to the script to fix this, but if anyone has already gone through this I'd appreciate the help.

Thx.

This seems to have worked.  I first had to drop the FK Constraint, then let it Alter the Users table...  then had to re-add the constraint.

At the very beginning of the 03.00.13.SqlDataProvider script I added:

ALTER TABLE DnnForge_NewsArticles_Article
 DROP CONSTRAINT FK_DnnForge_NewsArticles_Article_Users
GO

Then after this:

ALTER TABLE Users ADD CONSTRAINT
 PK_Users PRIMARY KEY CLUSTERED
 (
 UserID
 ) ON [PRIMARY]

GO

I added this to put the constraint back... did this with AuthorID... I hope that's right!!

ALTER TABLE DnnForge_NewsArticles_Article WITH NOCHECK ADD CONSTRAINT
 FK_DnnForge_NewsArticles_Article_Users FOREIGN KEY
 (
 AuthorID
 ) REFERENCES Users
 (
 UserID
 ) ON DELETE CASCADE
  NOT FOR REPLICATION
GO

Anyone care to verify?  SQL scripting is not my strong suit.  Drinking is......  

p.s.  I still get an error, unrelated I believe:

Server: Msg 2705, Level 16, State 4, Line 2
Column names in each table must be unique. Column name 'Email' in table 'Users' is specified more than once.

but I'm choosing to ignore it.