syspublications.name AS "Publication",
sysarticles.name AS "Article",
SELECT ', ' + syscolumns.name AS [text()]
FROM sysarticlecolumns WITH (NOLOCK)
INNER JOIN syscolumns WITH (NOLOCK) ON sysarticlecolumns.colid = syscolumns.colorder
WHERE sysarticlecolumns.artid = sysarticles.artid
AND sysarticles.objid = syscolumns.id
ORDER BY syscolumns.colorder
FOR XML PATH('')
), 1, 2, ''
) AS "Columns" FROM syspublications WITH (NOLOCK)
INNER JOIN sysarticles WITH (NOLOCK) ON syspublications.pubid = sysarticles.pubid
ORDER BY syspublications.name, sysarticles.name
--Find source and destination tables
SELECT art.name, art.dest_table, pub.name FROM sysarticles art , syspublications pub
WHERE art.pubid= pub.pubid
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.