Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Replication / August 2008

Tip: Looking for answers? Try searching our database.

generate scrip error

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
gremlin321 - 14 Aug 2008 20:31 GMT
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
Hilary Cotter - 16 Aug 2008 16:09 GMT
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?

>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
[quoted text clipped - 5 lines]
> 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
gremlin321 - 26 Aug 2008 16:27 GMT
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

> 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
[quoted text clipped - 15 lines]
> > 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
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.