New answers tagged

0

You can use the NOT VALID modifier when creating a foreign key to stop it verifying existing data. For instance: ALTER TABLE sales ADD CONSTRAINT sales_date_fk FOREIGN KEY (sale_date) REFERENCES dates (date_idx) NOT VALID; I would not recommend this though, unless something prevents you from populating the new child table so you have no choice. This is ...


1

From comments: This might happen due to the the value physically written on the page being incorrect (data corruption). Or a bug in the product (probably less likely but possible). Run DBCC CHECKDB to see if that finds any issues. – Martin Smith Jun 18 '16 at 0:07 3 Along Martin's comment - did the data get into the table via MERGE? Here is one bug (closed ...


-1

You can also do this: ALTER SEQUENCE 'sequence_name_goes_here' name" RESTART WITH (SELECT max(id) + 1 FROM 'table_name_goes_here');


2

ALTER TABLE [dbo].[Table1] CHECK CONSTRAINT [CHK_TOTALS] enables the constraint for all future updates to the table. Since you originally created that constraint WITH NOCHECK, existing at that time rows were not verified, and this applies (emphasis mine): WITH CHECK | WITH NOCHECK Specifies whether the data in the table is or isn't validated against a newly ...


Top 50 recent answers are included