>>Hi,
>>
>>I am going through a testing phase of converting a VFP database to SQL Server database. And I expect to have to truncate SQL tables maybe several times as I fix problems. But what happens is on the first truncate (even when ALL tables of SQL Server have no records) I get message that "truncate cannot be executed because table has FOREIGN KEY constraints". I understand that it is logical not to allow breaking of a foreign key constraint but the tables have no records/rows. Therefore at this point there should not be (at least IMHO) a reason not to allow truncate. What am I missing? TIA.
>
>You're not missing anything - that's the way it is:
http://msdn.microsoft.com/en-us/library/ms177570.aspx :
>"You cannot use TRUNCATE TABLE on tables that:
>Are referenced by a FOREIGN KEY constraint. (You can truncate a table that has a foreign key that references itself.)
>Participate in an indexed view.
>Are published by using transactional replication or merge replication.
>For tables with one or more of these characteristics, use the DELETE statement instead."
Ok; I will have to use DELETE. I would prefer to TRUNCATE since it resets the Identity column back to 0 too. But it is not such a big deal. Thank you for your help.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
