generate scrip error
in [Replication]
|
Prev: Transactional Replication Subscriber went missing after Timeout
Next: UDFs & Transactional Replication
From: gremlin321 on 14 Aug 2008 15:31 i have transactional replication that is running fine, the problem came out when we neededto move production server. as quick way to create scripts i used generate script wizard. in most cases it worked fine, however for a couple of tables that use procs instead of insert statements i had N'SQl' instead of the name of the procedure something like N'sp_MSupd....' is this expected behaviour or a bug? it looks like i have no other options at this point to go through every line of the script and verify names of procs created on subscribers
From: Hilary Cotter on 16 Aug 2008 11:09 I am not sure what you mean. Are you saying for the tables which were not using SQL Statements - in other words they were using procs - when you scripted it out it used procs? Or are you saying for table which were using procs, they were scripted out with SQL Statements? I can't repro your problem in SQL 2005. What version and sp of SQL are you running? "gremlin321" <gremlin321(a)discussions.microsoft.com> wrote in message news:9739E8FA-818B-408F-A46F-FF65B8294704(a)microsoft.com... >i have transactional replication that is running fine, the problem came out > when we neededto move production server. as quick way to create scripts i > used generate script wizard. in most cases it worked fine, however for a > couple of tables that use procs instead of insert statements i had N'SQl' > instead of the name of the procedure > something like N'sp_MSupd....' is this expected behaviour or a bug? it > looks > like i have no other options at this point to go through every line of the > script and verify names of procs created on subscribers
From: gremlin321 on 26 Aug 2008 11:27
what happens is i have one table that is replicated through the proc, the rest are set to replicate through the statements (insert;update;delete). when i generate script all tables come out as replicated through statements, something like @upd_cmd=N'SQL' instead of N'myprocname'. i am running 9.0.3175 "Hilary Cotter" wrote: > I am not sure what you mean. Are you saying for the tables which were not > using SQL Statements - in other words they were using procs - when you > scripted it out it used procs? > > Or are you saying for table which were using procs, they were scripted out > with SQL Statements? > > I can't repro your problem in SQL 2005. What version and sp of SQL are you > running? > > "gremlin321" <gremlin321(a)discussions.microsoft.com> wrote in message > news:9739E8FA-818B-408F-A46F-FF65B8294704(a)microsoft.com... > >i have transactional replication that is running fine, the problem came out > > when we neededto move production server. as quick way to create scripts i > > used generate script wizard. in most cases it worked fine, however for a > > couple of tables that use procs instead of insert statements i had N'SQl' > > instead of the name of the procedure > > something like N'sp_MSupd....' is this expected behaviour or a bug? it > > looks > > like i have no other options at this point to go through every line of the > > script and verify names of procs created on subscribers > |