September 2, 2009 at 2:17 am
TITLE: New Publication Wizard
------------------------------
New Publication Wizard encountered one or more errors while retrieving publication names.
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
Invalid column name 'snapshot_jobid'.
Invalid column name 'use_partition_groups'.
Invalid column name 'replicate_ddl'.
Invalid column name 'publication_number'.
Invalid column name 'allow_subscriber_initiated_snapshot'.
Invalid column name 'allow_web_synchronization'.
Invalid column name 'web_synchronization_url'.
Invalid column name 'allow_partition_realignment'.
Invalid column name 'retention_period_unit'.
Invalid column name 'decentralized_conflicts'.
Invalid column name 'generation_leveling_threshold'.
Invalid column name 'automatic_reinitialization_policy'.
Invalid column name 'snapshot_jobid'.
Invalid column name 'use_partition_groups'.
Invalid column name 'replicate_ddl'.
Invalid column name 'publication_number'.
Invalid column name 'allow_subscriber_initiated_snapshot'.
Invalid column name 'allow_web_synchronization'.
Invalid column name 'web_synchronization_url'.
Invalid column name 'allow_partition_realignment'.
Invalid column name 'retention_period_unit'.
Invalid column name 'decentralized_conflicts'.
Invalid column name 'generation_leveling_threshold'.
Invalid column name 'automatic_reinitialization_policy'. (Microsoft SQL Server, Error: 207)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1406&EvtSrc=MSSQLServer&EvtID=207&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
Please help me how to do with!
Very Thanks!
September 2, 2009 at 6:16 am
Did you upgrade the distributor as well? I think for replication to work when upgrading from 2000 to 2005, it should always be a in-place upgrade.
-Roy
September 3, 2009 at 2:46 am
Thanks Roy!
After I have upgraded SQL Server 2000 to 2005, I created a new distribution database.
I have deal with it.
Before I upgraded SQL Server, my database has been published.I created transactional replication and merge replication. when I upgraded SQL Server,I detached my database from the Server. after I upgraded SQL Server.I attach my database.
The following is what I do:
I first published the my databse,and in publisher properties I select my database transactional and merge.
November 13, 2009 at 8:40 am
[font="Arial"]
The issue arises because the database still contains the SQL2000 replication objects.
You don't have to move the database back to 2000 to fix it; you just have to remove all the existing replication objects from the database.
The following script accomplishes this task:
[/font]
[font="Courier New"]
-----------------------------------------------------------------------------------------------------
/*<Database Name> is a placeholder for name of the database you are trying to publish */
/*Remove the replication objects from the Database*/
Use [<Database Name>]
EXEC sp_removedbreplication @dbname = '<Database Name>'
GO
/*For good measure ensure that the database is not marked as a publisher in the master*/
USE [master]
DECLARE @publicationDB AS sysname;
SET @publicationDB = N'<Database Name>';
EXEC sp_replicationdboption
@dbname = @publicationDB,
@optname = N'publish',
@value = N'false';
GO
[/font]
Kurt Soutendijk
Sr SQL Server DBA/Developer
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply