all groups > sql server replication > january 2005 >
You're in the sql server replication group:
error 14058: The subscription already exists
sql server replication:
use this script on the subscriber, and then recreate and redistribute the snapshot. http://groups-beta.google.com/group/microsoft.public.sqlserver.replication/msg/39adc1169854d53a?dmode=source -- Hilary Cotter Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html [quoted text, click to view] "Warren Patterson" <des@newsgroups.nospam> wrote in message news:%23hZS85$8EHA.2012@TK2MSFTNGP15.phx.gbl... > Hi, > > I am using merge replication. The subscriber is using pull subscription. > > The problem is this; a subscriber machine has crashed. The problem is how > do i delete any evidence of the subscriber on the publisher, so that i can > create this subscriber again, without getting this error: "error 14058: The > subscription already exists" > > Any assistance would be greatly appreciated. > > > Kind Regards > Warren Patterson > >
Hi, I am using merge replication. The subscriber is using pull subscription. The problem is this; a subscriber machine has crashed. The problem is how do i delete any evidence of the subscriber on the publisher, so that i can create this subscriber again, without getting this error: "error 14058: The subscription already exists" Any assistance would be greatly appreciated. Kind Regards Warren Patterson
I'll rewrite it to address a specific article publication. Could you tell me the problem table/publication name? -- Hilary Cotter Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html [quoted text, click to view] "Warren Patterson" <des@newsgroups.nospam> wrote in message news:OXud%23AI9EHA.2452@TK2MSFTNGP14.phx.gbl... > Hi Hilary, > > Many thanks for you reply. > > From what you have said in the link, this will delete all publications, I > have 4 other publications and 4 other subscriptions on the server, so > following that route would not be a good idea, if its going to remove all > publications and subscriptions. > > Is there another way? > > Kind Regards > Warren Patterson > > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > news:OCfuaAA9EHA.3596@TK2MSFTNGP12.phx.gbl... > > use this script on the subscriber, and then recreate and redistribute the > > snapshot. > > > > > http://groups-beta.google.com/group/microsoft.public.sqlserver.replication/msg/39adc1169854d53a?dmode=source > > > > -- > > Hilary Cotter > > Looking for a SQL Server replication book? > > http://www.nwsu.com/0974973602.html > > "Warren Patterson" <des@newsgroups.nospam> wrote in message > > news:%23hZS85$8EHA.2012@TK2MSFTNGP15.phx.gbl... > > > Hi, > > > > > > I am using merge replication. The subscriber is using pull subscription. > > > > > > The problem is this; a subscriber machine has crashed. The problem is > how > > > do i delete any evidence of the subscriber on the publisher, so that i > can > > > create this subscriber again, without getting this error: "error 14058: > > The > > > subscription already exists" > > > > > > Any assistance would be greatly appreciated. > > > > > > > > > Kind Regards > > > Warren Patterson > > > > > > > > > > > >
Hi Hilary, Many thanks for you reply. From what you have said in the link, this will delete all publications, I have 4 other publications and 4 other subscriptions on the server, so following that route would not be a good idea, if its going to remove all publications and subscriptions. Is there another way? Kind Regards Warren Patterson [quoted text, click to view] "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message news:OCfuaAA9EHA.3596@TK2MSFTNGP12.phx.gbl... > use this script on the subscriber, and then recreate and redistribute the > snapshot. > > http://groups-beta.google.com/group/microsoft.public.sqlserver.replication/msg/39adc1169854d53a?dmode=source > > -- > Hilary Cotter > Looking for a SQL Server replication book? > http://www.nwsu.com/0974973602.html > "Warren Patterson" <des@newsgroups.nospam> wrote in message > news:%23hZS85$8EHA.2012@TK2MSFTNGP15.phx.gbl... > > Hi, > > > > I am using merge replication. The subscriber is using pull subscription. > > > > The problem is this; a subscriber machine has crashed. The problem is how > > do i delete any evidence of the subscriber on the publisher, so that i can > > create this subscriber again, without getting this error: "error 14058: > The > > subscription already exists" > > > > Any assistance would be greatly appreciated. > > > > > > Kind Regards > > Warren Patterson > > > > > >
can you enable logging and see exactly what the final error is? Also, you might want to try to drop this subscription, and then do a nosync subscription -- Hilary Cotter Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html [quoted text, click to view] "Warren Patterson" <des@newsgroups.nospam> wrote in message news:eJ5euox9EHA.1392@tk2msftngp13.phx.gbl... > Sorry regarding my previous post, I meant to say > > "..... Seemed to setup everything okay. But now another problem has > occurred, I will post this under a new topic, "the process could not query > row metadata at the subscriber"......." > > > > > > > > > "Warren Patterson" <des@newsgroups.nospam> wrote in message > news:u0mCjax9EHA.3368@TK2MSFTNGP15.phx.gbl... > > Hi Hilary, > > > > That wont be necessary, I have managed to get around this. I simply > copied > > everything from the subscriber from the mssql\data folder and overwrote > the > > new subscriber mssql\data folder. Seemed to setup everything okay. But > now > > another problem has occurred, I will post this under a new topic, but for > > now, its this > > > > "the process could not query row metadata at the subscriber" > > > > I have seen previous posts by yourself, mentioning to increase > queryTimeout, > > but this has not helped me in anyway. Do you have any other suggestions? > > Please see my new post title "the process could not query row metadata at > > the subscriber" > > > > Many thanks again for your help. > > > > Kind Regards > > Warren > > > > > > > > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > > news:uF82xYL9EHA.2900@TK2MSFTNGP09.phx.gbl... > > > I'll rewrite it to address a specific article publication. Could you > tell > > me > > > the problem table/publication name? > > > > > > -- > > > Hilary Cotter > > > Looking for a SQL Server replication book? > > > http://www.nwsu.com/0974973602.html > > > "Warren Patterson" <des@newsgroups.nospam> wrote in message > > > news:OXud%23AI9EHA.2452@TK2MSFTNGP14.phx.gbl... > > > > Hi Hilary, > > > > > > > > Many thanks for you reply. > > > > > > > > From what you have said in the link, this will delete all > publications, > > I > > > > have 4 other publications and 4 other subscriptions on the server, so > > > > following that route would not be a good idea, if its going to remove > > all > > > > publications and subscriptions. > > > > > > > > Is there another way? > > > > > > > > Kind Regards > > > > Warren Patterson > > > > > > > > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > > > > news:OCfuaAA9EHA.3596@TK2MSFTNGP12.phx.gbl... > > > > > use this script on the subscriber, and then recreate and > redistribute > > > the > > > > > snapshot. > > > > > > > > > > > > > > > > > > > > http://groups-beta.google.com/group/microsoft.public.sqlserver.replication/msg/39adc1169854d53a?dmode=source > > > > > > > > > > -- > > > > > Hilary Cotter > > > > > Looking for a SQL Server replication book? > > > > > http://www.nwsu.com/0974973602.html > > > > > "Warren Patterson" <des@newsgroups.nospam> wrote in message > > > > > news:%23hZS85$8EHA.2012@TK2MSFTNGP15.phx.gbl... > > > > > > Hi, > > > > > > > > > > > > I am using merge replication. The subscriber is using pull > > > subscription. > > > > > > > > > > > > The problem is this; a subscriber machine has crashed. The > problem > > is > > > > how > > > > > > do i delete any evidence of the subscriber on the publisher, so > that > > i > > > > can > > > > > > create this subscriber again, without getting this error: "error > > > 14058: > > > > > The > > > > > > subscription already exists" > > > > > > > > > > > > Any assistance would be greatly appreciated. > > > > > > > > > > > > > > > > > > Kind Regards > > > > > > Warren Patterson > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Hi Hilary, That wont be necessary, I have managed to get around this. I simply copied everything from the subscriber from the mssql\data folder and overwrote the new subscriber mssql\data folder. Seemed to setup everything okay. But now another problem has occurred, I will post this under a new topic, but for now, its this "the process could not query row metadata at the subscriber" I have seen previous posts by yourself, mentioning to increase queryTimeout, but this has not helped me in anyway. Do you have any other suggestions? Please see my new post title "the process could not query row metadata at the subscriber" Many thanks again for your help. Kind Regards Warren [quoted text, click to view] "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message news:uF82xYL9EHA.2900@TK2MSFTNGP09.phx.gbl... > I'll rewrite it to address a specific article publication. Could you tell me > the problem table/publication name? > > -- > Hilary Cotter > Looking for a SQL Server replication book? > http://www.nwsu.com/0974973602.html > "Warren Patterson" <des@newsgroups.nospam> wrote in message > news:OXud%23AI9EHA.2452@TK2MSFTNGP14.phx.gbl... > > Hi Hilary, > > > > Many thanks for you reply. > > > > From what you have said in the link, this will delete all publications, I > > have 4 other publications and 4 other subscriptions on the server, so > > following that route would not be a good idea, if its going to remove all > > publications and subscriptions. > > > > Is there another way? > > > > Kind Regards > > Warren Patterson > > > > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > > news:OCfuaAA9EHA.3596@TK2MSFTNGP12.phx.gbl... > > > use this script on the subscriber, and then recreate and redistribute > the > > > snapshot. > > > > > > > > > http://groups-beta.google.com/group/microsoft.public.sqlserver.replication/msg/39adc1169854d53a?dmode=source > > > > > > -- > > > Hilary Cotter > > > Looking for a SQL Server replication book? > > > http://www.nwsu.com/0974973602.html > > > "Warren Patterson" <des@newsgroups.nospam> wrote in message > > > news:%23hZS85$8EHA.2012@TK2MSFTNGP15.phx.gbl... > > > > Hi, > > > > > > > > I am using merge replication. The subscriber is using pull > subscription. > > > > > > > > The problem is this; a subscriber machine has crashed. The problem is > > how > > > > do i delete any evidence of the subscriber on the publisher, so that i > > can > > > > create this subscriber again, without getting this error: "error > 14058: > > > The > > > > subscription already exists" > > > > > > > > Any assistance would be greatly appreciated. > > > > > > > > > > > > Kind Regards > > > > Warren Patterson > > > > > > > > > > > > > > > > > > > >
Sorry regarding my previous post, I meant to say "..... Seemed to setup everything okay. But now another problem has occurred, I will post this under a new topic, "the process could not query row metadata at the subscriber"......." [quoted text, click to view] "Warren Patterson" <des@newsgroups.nospam> wrote in message news:u0mCjax9EHA.3368@TK2MSFTNGP15.phx.gbl... > Hi Hilary, > > That wont be necessary, I have managed to get around this. I simply copied > everything from the subscriber from the mssql\data folder and overwrote the > new subscriber mssql\data folder. Seemed to setup everything okay. But now > another problem has occurred, I will post this under a new topic, but for > now, its this > > "the process could not query row metadata at the subscriber" > > I have seen previous posts by yourself, mentioning to increase queryTimeout, > but this has not helped me in anyway. Do you have any other suggestions? > Please see my new post title "the process could not query row metadata at > the subscriber" > > Many thanks again for your help. > > Kind Regards > Warren > > > > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > news:uF82xYL9EHA.2900@TK2MSFTNGP09.phx.gbl... > > I'll rewrite it to address a specific article publication. Could you tell > me > > the problem table/publication name? > > > > -- > > Hilary Cotter > > Looking for a SQL Server replication book? > > http://www.nwsu.com/0974973602.html > > "Warren Patterson" <des@newsgroups.nospam> wrote in message > > news:OXud%23AI9EHA.2452@TK2MSFTNGP14.phx.gbl... > > > Hi Hilary, > > > > > > Many thanks for you reply. > > > > > > From what you have said in the link, this will delete all publications, > I > > > have 4 other publications and 4 other subscriptions on the server, so > > > following that route would not be a good idea, if its going to remove > all > > > publications and subscriptions. > > > > > > Is there another way? > > > > > > Kind Regards > > > Warren Patterson > > > > > > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > > > news:OCfuaAA9EHA.3596@TK2MSFTNGP12.phx.gbl... > > > > use this script on the subscriber, and then recreate and redistribute > > the > > > > snapshot. > > > > > > > > > > > > > > http://groups-beta.google.com/group/microsoft.public.sqlserver.replication/msg/39adc1169854d53a?dmode=source > > > > > > > > -- > > > > Hilary Cotter > > > > Looking for a SQL Server replication book? > > > > http://www.nwsu.com/0974973602.html > > > > "Warren Patterson" <des@newsgroups.nospam> wrote in message > > > > news:%23hZS85$8EHA.2012@TK2MSFTNGP15.phx.gbl... > > > > > Hi, > > > > > > > > > > I am using merge replication. The subscriber is using pull > > subscription. > > > > > > > > > > The problem is this; a subscriber machine has crashed. The problem > is > > > how > > > > > do i delete any evidence of the subscriber on the publisher, so that > i > > > can > > > > > create this subscriber again, without getting this error: "error > > 14058: > > > > The > > > > > subscription already exists" > > > > > > > > > > Any assistance would be greatly appreciated. > > > > > > > > > > > > > > > Kind Regards > > > > > Warren Patterson > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Hi, I enabled logging and this is the ouput (see below): Kind Regards Warren Patterson ****************************************************************** ****************************************************************** ****************************************************************** Microsoft SQL Server Merge Agent 8.00.760 Copyright (c) 2000 Microsoft Corporation Microsoft SQL Server Replication Agent: GENCENTRIC_SVR1-TGPS_LIVE-TGPS_LIVE_GN-GOKWENORTHSVR1-TGPS_LIVE_GN_SUBSCRIPT I- 0 Percent Complete: 0 Connecting to Subscriber 'GOKWENORTHSVR1' Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION' Server: GOKWENORTHSVR1 DBMS: Microsoft SQL Server Version: 08.00.0760 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [1/10/2005 4:28:27 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call sp_MSgetversion } [1/10/2005 4:28:27 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {?=call sp_helpsubscription_properties (N'GENCENTRIC_SVR1', N'TGPS_LIVE', N'TGPS_LIVE_GN')} Distributor security mode: 0, login name: sa, password: ********. [1/10/2005 4:28:27 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {?=call sp_helpsubscription_properties (N'GENCENTRIC_SVR1', N'TGPS_LIVE', N'TGPS_LIVE_GN')} Publisher security mode: 0, login name: sa, password: *********. Percent Complete: 0 Connecting to Distributor 'GENCENTRIC_SVR1' Connecting to Distributor 'GENCENTRIC_SVR1.' Server: GENCENTRIC_SVR1 DBMS: Microsoft SQL Server Version: 08.00.0760 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [1/10/2005 4:28:27 PM]GENCENTRIC_SVR1.: {call sp_MSgetversion } [1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.: {call sp_helpdistpublisher (N'GENCENTRIC_SVR1') } [1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.distribution: select datasource, srvid from master..sysservers where upper(srvname) = upper(N'GENCENTRIC_SVR1') [1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.distribution: {call sp_MSadd_merge_anonymous_agent(N'0', N'TGPS_LIVE', N'TGPS_LIVE_GN', N'TGPS_LIVE_GN_SUBSCRIPTION', N'GOKWENORTHSVR1',?, 5587)} [1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.distribution: {call sp_MShelp_profile (34, 4, N'')} Percent Complete: 0 Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE' Initializing Percent Complete: 1 Connecting to Publisher 'GENCENTRIC_SVR1' Server: GENCENTRIC_SVR1 DBMS: Microsoft SQL Server Version: 08.00.0760 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [1/10/2005 4:28:31 PM]GENCENTRIC_SVR1.TGPS_LIVE: set nocount on declare @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) select @collation = convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select collationproperty(@collation, N'CODEPAGE') as 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle' Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE' Server: GENCENTRIC_SVR1 DBMS: Microsoft SQL Server Version: 08.00.0760 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [1/10/2005 4:28:31 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion } Percent Complete: 3 Retrieving publication information Percent Complete: 4 Retrieving subscription information Percent Complete: 4 The merge process is cleaning up meta data in database 'TGPS_LIVE'. Percent Complete: 4 The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s) in MSmerge_contents, and 0 row(s) in MSmerge_tombstone. Percent Complete: 4 The merge process is cleaning up meta data in database 'TGPS_LIVE_GN_SUBSCRIPTION'. Percent Complete: 4 The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s) in MSmerge_contents, and 0 row(s) in MSmerge_tombstone. Percent Complete: 4 Uploading data changes to the Publisher Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION' Server: GOKWENORTHSVR1 DBMS: Microsoft SQL Server Version: 08.00.0760 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [1/10/2005 4:28:42 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call sp_MSgetversion } Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE' Server: GENCENTRIC_SVR1 DBMS: Microsoft SQL Server Version: 08.00.0760 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [1/10/2005 4:28:42 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion } Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION' Server: GOKWENORTHSVR1 DBMS: Microsoft SQL Server Version: 08.00.0760 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [1/10/2005 4:28:43 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call sp_MSgetversion } Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE' Server: GENCENTRIC_SVR1 DBMS: Microsoft SQL Server Version: 08.00.0760 user name: dbo
Not to worry, problem located, seems that the a table is corrupt and causing the "communication link failure" The error was very obscure, pointing me in teh wrong direction, I thought it was a network issue, it wasnt, it was a corrupt table. Now I have the "joy" of trying to recover data :-( [quoted text, click to view] "Warren Patterson" <des@newsgroups.nospam> wrote in message news:OoscZ869EHA.1396@tk2msftngp13.phx.gbl... > Hi, > > I enabled logging and this is the ouput (see below): > > Kind Regards > Warren Patterson > > > ****************************************************************** > ****************************************************************** > ****************************************************************** > Microsoft SQL Server Merge Agent 8.00.760 > Copyright (c) 2000 Microsoft Corporation > Microsoft SQL Server Replication Agent: > GENCENTRIC_SVR1-TGPS_LIVE-TGPS_LIVE_GN-GOKWENORTHSVR1-TGPS_LIVE_GN_SUBSCRIPT > I- 0 > > Percent Complete: 0 > Connecting to Subscriber 'GOKWENORTHSVR1' > Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION' > > Server: GOKWENORTHSVR1 > DBMS: Microsoft SQL Server > Version: 08.00.0760 > user name: dbo > API conformance: 2 > SQL conformance: 1 > transaction capable: 2 > read only: N > identifier quote char: " > non_nullable_columns: 1 > owner usage: 31 > max table name len: 128 > max column name len: 128 > need long data len: Y > max columns in table: 1024 > max columns in index: 16 > max char literal len: 524288 > max statement len: 524288 > max row size: 524288 > > [1/10/2005 4:28:27 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call > sp_MSgetversion } > [1/10/2005 4:28:27 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {?=call > sp_helpsubscription_properties (N'GENCENTRIC_SVR1', N'TGPS_LIVE', > N'TGPS_LIVE_GN')} > Distributor security mode: 0, login name: sa, password: ********. > [1/10/2005 4:28:27 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {?=call > sp_helpsubscription_properties (N'GENCENTRIC_SVR1', N'TGPS_LIVE', > N'TGPS_LIVE_GN')} > Publisher security mode: 0, login name: sa, password: *********. > Percent Complete: 0 > Connecting to Distributor 'GENCENTRIC_SVR1' > Connecting to Distributor 'GENCENTRIC_SVR1.' > > Server: GENCENTRIC_SVR1 > DBMS: Microsoft SQL Server > Version: 08.00.0760 > user name: dbo > API conformance: 2 > SQL conformance: 1 > transaction capable: 2 > read only: N > identifier quote char: " > non_nullable_columns: 1 > owner usage: 31 > max table name len: 128 > max column name len: 128 > need long data len: Y > max columns in table: 1024 > max columns in index: 16 > max char literal len: 524288 > max statement len: 524288 > max row size: 524288 > > [1/10/2005 4:28:27 PM]GENCENTRIC_SVR1.: {call sp_MSgetversion } > [1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.: {call sp_helpdistpublisher > (N'GENCENTRIC_SVR1') } > [1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.distribution: select datasource, srvid > from master..sysservers where upper(srvname) = upper(N'GENCENTRIC_SVR1') > [1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.distribution: {call > sp_MSadd_merge_anonymous_agent(N'0', N'TGPS_LIVE', N'TGPS_LIVE_GN', > N'TGPS_LIVE_GN_SUBSCRIPTION', N'GOKWENORTHSVR1',?, 5587)} > [1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.distribution: {call sp_MShelp_profile > (34, 4, N'')} > Percent Complete: 0 > Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE' > Initializing > Percent Complete: 1 > Connecting to Publisher 'GENCENTRIC_SVR1' > > Server: GENCENTRIC_SVR1 > DBMS: Microsoft SQL Server > Version: 08.00.0760 > user name: dbo > API conformance: 2 > SQL conformance: 1 > transaction capable: 2 > read only: N > identifier quote char: " > non_nullable_columns: 1 > owner usage: 31 > max table name len: 128 > max column name len: 128 > need long data len: Y > max columns in table: 1024 > max columns in index: 16 > max char literal len: 524288 > max statement len: 524288 > max row size: 524288 > > [1/10/2005 4:28:31 PM]GENCENTRIC_SVR1.TGPS_LIVE: set nocount on declare > @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) > select @collation = convert(nvarchar(255), databasepropertyex(@dbname, > N'COLLATION')) select collationproperty(@collation, N'CODEPAGE') as > 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', > collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle' > Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE' > > Server: GENCENTRIC_SVR1 > DBMS: Microsoft SQL Server > Version: 08.00.0760 > user name: dbo > API conformance: 2 > SQL conformance: 1 > transaction capable: 2 > read only: N > identifier quote char: " > non_nullable_columns: 1 > owner usage: 31 > max table name len: 128 > max column name len: 128 > need long data len: Y > max columns in table: 1024 > max columns in index: 16 > max char literal len: 524288 > max statement len: 524288 > max row size: 524288 > > [1/10/2005 4:28:31 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion } > Percent Complete: 3 > Retrieving publication information > Percent Complete: 4 > Retrieving subscription information > Percent Complete: 4 > The merge process is cleaning up meta data in database 'TGPS_LIVE'. > Percent Complete: 4 > The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s) in > MSmerge_contents, and 0 row(s) in MSmerge_tombstone. > Percent Complete: 4 > The merge process is cleaning up meta data in database > 'TGPS_LIVE_GN_SUBSCRIPTION'. > Percent Complete: 4 > The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s) in > MSmerge_contents, and 0 row(s) in MSmerge_tombstone. > Percent Complete: 4 > Uploading data changes to the Publisher > Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION' > > Server: GOKWENORTHSVR1 > DBMS: Microsoft SQL Server > Version: 08.00.0760 > user name: dbo > API conformance: 2 > SQL conformance: 1 > transaction capable: 2 > read only: N > identifier quote char: " > non_nullable_columns: 1 > owner usage: 31 > max table name len: 128 > max column name len: 128 > need long data len: Y > max columns in table: 1024 > max columns in index: 16 > max char literal len: 524288 > max statement len: 524288 > max row size: 524288 > > [1/10/2005 4:28:42 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call > sp_MSgetversion } > Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE' > > Server: GENCENTRIC_SVR1 > DBMS: Microsoft SQL Server > Version: 08.00.0760 > user name: dbo > API conformance: 2 > SQL conformance: 1 > transaction capable: 2 > read only: N > identifier quote char: " > non_nullable_columns: 1 > owner usage: 31 > max table name len: 128 > max column name len: 128 > need long data len: Y > max columns in table: 1024 > max columns in index: 16 > max char literal len: 524288 > max statement len: 524288 > max row size: 524288 >
Don't see what you're looking for? Try a search.
|
|
|