DBA's always face problem with Indentiy columns in replications. Following scripts will list all identity columns in current database with the value of 'Not For Replication'.
SELECT OBJECT_NAME(OBJECT_ID) AS TABLENAME,
c.Name as COLUMNNAME,
WHEN 1 THEN 'YES'
END as 'NotForReplication'
FROM SYS.IDENTITY_COLUMNS c JOIN sysobjects so (NOLOCK) ON so.id = c.OBJECT_ID
WHERE OBJECT_NAME(OBJECT_ID) not in ('dtproperties')
and OBJECT_NAME(OBJECT_ID) not like ('MSMerg%')
and OBJECT_NAME(OBJECT_ID) not like ('SysMerg%')
and so.type = 'u'
ORDER BY 1
Changing a replicated table in SQL 7 was a lot of work. SQL 2000 offers some help, but in many cases it's not enough. This article by Andy Warren shows you which changes SQL 2000 will help you with and which ones it won't.
In this product review Andy takes a look at Data Compare, the second of three products in the SQL Bundle available from Red-Gate software. It's a very handy program that lets you compare data between two tables and optionally generate sql statements to syncronize the data. An interesting alternative to replication!
Microsoft® SQL Server™ 2000 allows you to restore transactional replication databases without reinitializing subscriptions or disabling and reconfiguring publishing and distribution. You can set up replication to work with log shipping, enabling you to use a warm standby server without reconfiguring replication.