Activity overview
Latest activity by katokay
Yes, it works and that must have been it. I have recently restored from a backup and apparently it was using the old information. Sorry for the false alarm. / comments
Yes, it works and that must have been it. I have recently restored from a backup and apparently it was using the old information. Sorry for the false alarm.
CREATE TABLE [dbo].[Address]
(
[addressId] [int] NOT NULL IDENTITY(1, 1),
[line1StreetAddress] [varchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[line2StreetAddress] [varchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[cityName] [varchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[zipCode] [varchar] (10) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[stateCode] [char] (2) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[countyName] [varchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL
)
Above is what is shown in my DDL view when in fact it should look like this.
CREATE TABLE [dbo].[Address]
(
[addressId] [int] NOT NULL IDENTITY(1, 4),
[line1StreetAddress] [varchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[line2StreetAddress] [varchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[cityName] [varchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[zipCode] [varchar] (10) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[stateCode] [char] (2) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[countyName] [varchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL
) / comments
CREATE TABLE [dbo].[Address]
(
[addressId] [int] NOT NULL IDENTITY(1, 1),
[line1StreetAddress] [varchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[line2StreetAddress] [varchar] (100) COLLAT...
DDL view incorrect identity increment value
When an increment other than 1 is used for an identity field, the ddl view still always shows (1,1).