Comments
Sort by recent activity
Yes it puts the WITH (STATISTICS_NORECOMPUTE=ON)
on the source and destination Constraints and Indexes. / comments
Yes it puts the WITH (STATISTICS_NORECOMPUTE=ON)
on the source and destination Constraints and Indexes.
Hi,
I can confirm that the STATISTICS_NORECOMPUTE=ON isn't set on the SQL SERVER 2005 table, SQL Compare seems to add it on.
Below is an example of where it added it to the source table "Constraints and Indexes" window.
ALTER TABLE [dbo].[CodesArea] ADD CONSTRAINT [IX_CodesArea] UNIQUE NONCLUSTERED ([AreaCode]) WITH (STATISTICS_NORECOMPUTE=ON)
The ignore indexes would be no good for us. / comments
Hi,
I can confirm that the STATISTICS_NORECOMPUTE=ON isn't set on the SQL SERVER 2005 table, SQL Compare seems to add it on.
Below is an example of where it added it to the source table "Constraint...
1) When I script the table out from Sql Server 2005 it doesn't have STATISTICS_NORECOMPUTE
2) I don't have two SQL 2005 database to compare, it's a locked down environment so I can't easily do this.
3) I'm comparing the same database schema between dev & uat. Dev is SQL 2005 and UAT is 2000. Both are populated with the sames tables and data. / comments
1) When I script the table out from Sql Server 2005 it doesn't have STATISTICS_NORECOMPUTE
2) I don't have two SQL 2005 database to compare, it's a locked down environment so I can't easily do this...