Manuals / Sybase / Personal Care / Microscope & Magnifier

Sybase DC38133-01-0902-01 manual Running multiple Message Agents

Models: DC38133-01-0902-01

1 485

Download 485 pages 33.95 Kb

Page 287

Chapter 12. Administering SQL Remote for Adaptive Server

Enterprise

Running the Message Agent

This section describes how to run the Message Agent for Adaptive Server Enterprise. For information on features of the Message Agent that are common to Adaptive Server Anywhere and Adaptive Server Enterprise, see “Running the Message Agent” on page 223 .

The Message Agent and replication security

In the tutorials earlier in this book, the Message Agent was run using a user ID with system administrator permissions. The operations in the messages are carried out from the user ID speciﬁed in the Message Agent connection string; by using a system administrator user ID, you can be sure that the user has permissions to make all the changes.

In practice, you will not use such a user ID, but the Message Agent needs to run using a user ID with replication role. You can grant replication role with the following statement:

sp_role ’grant’, replication_role, user_name

The user for the Message Agent must have insert, update and delete permissions on all replicated tables, in order to apply the changes. Also, the replication error procedure must be created under the Message Agent user ID.

When you setup your Adaptive Server Enterprise database, the scripts ssremote.sql and squeue.sql must be run under the same user name you use for the Message Agent.

☞For setup instructions, see “Setting Up SQL Remote” on page 19 .

To hide the user password for the Message Agent user ID, you can store the ssremote command-line options in a ﬁle, and use ssremote with the @data parameter. You can use ﬁle system security to prevent unauthorized access to the ﬁle.

Running multiple Message Agents

The three phases of Message Agent operation are described in the section “Message Agent operation phases” on page 266 . To summarize, these phases are:

♦Receiving messages.

♦Scanning the transaction log.

♦Sending messages.

269

Image 287

Sybase DC38133-01-0902-01 manual Running multiple Message Agents, For setup instructions, see Setting Up SQL Remote on

Contents

Part number DC38133-01-0902-01 Last modiﬁed October SQL Remote User’s GuidePage Contents SQL Remote Design for Adaptive Server Enterprise 141 SQL Remote Administration 199Principles of SQL Remote Design SQL Remote Design for Adaptive Server AnywhereUtilities and Options Reference 291 Administering SQL Remote for Adaptive Server Anywhere241Using SQL Remote with Replication Server 277 System Objects for Adaptive Server Anywhere 325Command Reference for Adaptive Server Enterprise 379 Command Reference for Adaptive Server Anywhere 353Index 449 Server Anywhere Differences 437SQL Remote for Adaptive Server Enterprise and Adaptive Supported Platforms and Message Links 445Viii Systems About This ManualMail or ﬁle transfer Adaptive Server Anywhere Database Administration Guide This SQL Anywhere Studio documentationPage Page Release Savepoint savepoint-name Documentation conventionsXiv Following icons are used in this documentationClient application Database server, such as Sybase Adaptive Server AnywhereAsademo.db Adaptive Server Anywhere sample databaseFinding out more and providing feedback Page Xviii Introduction to SQL Remote Page This chapter introduces SQL Remote and the documentation Welcome to SQL RemoteAbout SQL Remote SQL Remote for Adaptive Server Anywhere Enables replicationAbout this manual Product installationTo install the SQL Remote software Windows To install the SQL Remote software UnixPage SQL Remote SQL Remote ConceptsSQL Remote components Message Agent Data serverClient applications Message system client Two-table synchronization definition Publications and subscriptionsAt the remote database ReplicationSQL Remote features Page Server-to-laptop replication for mobile workforces Some sample installationsServer-to-server replication among ofﬁces More Page Setting Up SQL Remote You must take some steps to Setup overviewEach user in the installation Sybase System Administrator should perform all SQL RemoteEnsuring Tempdb is large enough Installing the SQL Remote system objectsTo install the SQL Remote system objects Preparing your Adaptive Server Enterprise serverSQL Remote system objects To install the stable queue Command-line installation of the stable queuePage Upgrading SQL Remote for Adaptive Server Enterprise To upgrade SQL RemoteTo uninstall the stable queue from a database Uninstalling SQL RemoteTo uninstall the SQL Remote objects from a database Tutorials for Adaptive Server Anywhere Users Database Just on those issues important for replicationIntroduction GoalsTables are described in more detail as follows Tutorials for Adaptive Server Anywhere UsersCustkey Replication goalsRepkey NameSybase Central or command-line utilities To prepare for the tutorial Preparing for the Sybase Central replication tutorialTo add tables to the consolidated database Add a SQL Remote message type Setting up a consolidated databaseAdd the publisher and remote user to the database To add an address to a message typeTo create a new user as the publisher To add a publication To add a remote userAdd publications and subscriptions Publication for the remote database user ﬁelduser Set up the remote database in Sybase CentralEnter the expression repkey Click Finish to create the publicationTo extract a database To create the databases and directories for the tutorial Preparing for the replication tutorialCreate a SQL Remote message type Set up the consolidated databaseTo add the tables to the consolidated database To create a publisher for the database To create the message typeGrant Publish and Remote at the consolidated database Table SalesRep, and some of the rows of the table Customer Create publications and subscriptionsSQL, to create a publication To create the subscription Set up the remote databaseTo create the publication To load the database information Extract the remote database informationLoad the remote database information Select * from SalesRep Select * from Customer First, enter some data into the consolidated database Start replicating dataEnter data at the consolidated database Send data from the consolidated databaseTo receive data at the remote database Receive data at the remote databaseTo send the data to the remote database Commit the insertion by executing the following statement To verify that the data has arrivedCustkey Name Repkey To add the publication to the sample database Sample publicationPage Tutorial for Adaptive Server Enterprise Users Database schema for the tutorial is illustrated in the ﬁgure SalesRep table is many-to-one Tutorial for Adaptive Server Enterprise UsersPage First steps Tutorial Adaptive Server Enterprise replicationTo install SQL Remote into the hq database Create the Customer table with the following statement Setting up the consolidated databaseCreate the SalesRep table with the following statement Create the necessary users and permissions Create the message links and addressesTo create the subscriber To create the publisherCreate an empty publication Create the publication and subscriptionExtract the remote database To create a subscriptionCreate a subscription to SalesRepData for ﬁelduser , with a Subscription value of rep1To create a database ﬁle named ﬁeld.db To load the data into the database using Interactive SQLUtility on Run the script from Interactive SQL Connect to the server using the Interactive SQL utilityTo load the data into the database as a batch process Connect to the Adaptive Server Enterprise server from isql To enter data at the Adaptive Server Enterprise databaseTo receive the data at Adaptive Server Anywhere To replicate the data from Adaptive Server EnterpriseCommit the row Custkey Name Repkey Page Replication Design for SQL Remote Page Principles of SQL Remote Design SQL Remote replicates data Adaptive Server Enterprise System Administrator or databaseDesign overview Ensuring compatible databasesBetween Ssremote and Adaptive Server Enterprise whenever Using compatible sort orders and character setsSQL Remote Message Agent does not perform any character set Conversions819LATIN1 Eucjapan Replication of inserts and deletes Replication of updatesHow statements are replicated Representatives Clause of the Update statementUser, the row to be updated is not found StatementReplication of triggers Replication of proceduresThis case, the Update does not update anything Procedure call is not replicatedSome Before triggers can produce Message causing the conﬂictBody of your triggers Actions carried out by conﬂictReplication of data deﬁnition statements Replication of blobs How data types are replicatedReplication of dates and times Select Who gets what? Principles of SQL Remote Design Replication conﬂicts Replication errors and conﬂictsReplication errors Detected Tracking SQL errorsIssue the following statement VARCHAR, or Long VARCHAR. The procedure is called once withPage SQL Remote Design for Adaptive Server Anywhere Information each user receives Publications determine what informationIs shared among which databases Subscriptions determine whatTo publish one or more entire tables SQL Publishing dataPublishing whole tables To publish one or more entire tables Sybase CentralTo publish only some columns in a table Sybase Central Publishing only some columns in a tableFor more information, see the Create Publication statement To publish only some columns in a table SQL Publishing only some rows in a tableTo create a publication using a Where clause SQL Publishing only some rows using a Where clauseTo create a publication using a Where clause Sybase Central Publishing only some rows using a subscription expression Column To create an article using a subscription expression SQLTo add articles Sybase Central Altering existing publicationsTo modify an existing publication SQL Dropping publicationsTo remove articles Sybase Central See also the Drop Publication statement ASA SQL Reference, To delete a publication Sybase CentralTo delete a publication SQL Publication design for Adaptive Server Anywhere Design issues overviewDesign tips for performance Conditions for valid articlesPay attention to Update Publication Triggers In particular Three tables are described in more detail as follows Here is a simple database that illustrates the problemContact example 106 Following informationThose customers assigned to them, from the Customer table Territory realignment in the Contact example Partitioning the Customer table in the Contact examplePartitioning the Contact table in the Contact example For which there is no longer a Customer RepsProperly transferred to the new sales representative Along with the CustomerSpecial Update statement for publications ∙ Customer table Understanding this helps in designing efﬁcient publicationsAssume the following data ∙ SalesRep tableSalesRepData Publication Name rep1 Before list Many-to-many relationship in the database Sharing rows among several subscriptionsPolicy example 113 With the following informationEntire SalesRep table Involving the sales rep subscribed to the dataPublication Contact example on Territory realignment with a many-to-many relationship116 Remote databases contain the proper dataDealing with the customer, taken from the Policy table Customer being transferred Where custkey = OldRow.custkeyThat this subquery can be multi-valued Can be multi-valuedCustomer SQL Remote Design for Adaptive Server Anywhere ID Rep Dept Ann Marc Managing conﬂictsUpdating Must be excluded from the installation by proper designSQL Remote installation at the consolidated database How SQL Remote handles conﬂictsUsing conﬂict resolution triggers Implementing conﬂict resolutionReferencing OLD AS oldval Create Trigger trigger-nameResolving date conﬂicts Conﬂict resolution examplesResolving inventory conﬂicts Reporting conﬂicts Increments from the two updates. For exampleIncludes the salesorder table Designing to avoid referential integrity errorsDesigning triggers to avoid errors Page Ensuring unique primary keys Using global autoincrement default column valuesSetting the Globaldatabaseid value Declaring default global autoincrementDatabase will have Globaldatabaseid set to Primary key values for Global Default Autoincrement valuesTo set the global database identiﬁcation number How default values are chosen Using primary key pools To replicate the primary key pool SQL Primary key pool tableReplicating the primary key pool Filling and replenishing the key pool Cursor for 136Else Adding new customersInsert Primary key pool summaryTo create and manage subscriptions in Sybase Central Creating subscriptions140 For more information, see Create Subscription statement on141 SQL Remote Design for Adaptive Server EnterpriseDesign overview Creating articles containing some of the columns in a table Creating publicationsCreating whole-table articles Creating articles containing some of the rows in a table Creating an article using a subscription column Creating an article using a Where clauseTo create an article using a Where clause Spaddarticle publicationname, tablename NULL, columnname To create an article using a subscription columnSpaddremotetable tablename Publication design for Adaptive Server Enterprise Insert Succeeds 149 To handle this case, using an exampleContain the subscription column Two tables described earlier in this chapter150 Are realigned Exec spcreatepublication ’SalesRepData’ go Adding a subscription-list column to the Contact tableLog entries are values, not subscribers For the following operations Update on the Contact tableUpdate on the Customer table Maintaining the subscription-list columnSQL Remote Design for Adaptive Server Enterprise Tuning extraction performance156 To create a subscription viewCreate a view that contains this subquery. For example Solving the problem Foreign KEY 158159 Subscriptions to this publication take the following formThese objects Triggers For Insert AS Begin 161Ensure the quotedidentiﬁer option is set to on Tuning extraction performance for shared rows163 Customer Managing conﬂicts When the conﬂicting message arrived Consolidated database, no row will be updatedAny conﬂict resolution procedures are called Database objects to handle the resolutionThis table must have the same column names Names of the conﬂict resolution objectsRemoterowtable. These three are discussed in turn Table only ever contains a single row168 ﬁrst conﬂict resolution exampleTwo-table database is as follows @lostname value is the value that was overridden by Conﬂict-causing UpdateAfter the procedure is run, the rows in the OldCustomer FollowsConﬂictLog table has a single row, showing the conﬂict Second conﬂict resolution exampleTo test the example Replaces it with the value that was previously present It when the procedure is executedLost and won names User ID of the remote user. The table is as followsCurrentremoteuser column of the temporary table #remote Where conﬂict resolution is carried out by Before triggersThere are several points of note here User ID of the remote user is stored by the Message Agent173 Page Columns of this table have the following meanings 175 Primary key pool176 To replicate the primary key pool177 Adding new customers 179 Testing the key poolTo test the primary key pool Primary key pool summary Spsubscription create, puborders SamS ’856’ Page SQL Remote Page 185 SQL Remote replication installationDeploying and Synchronizing Databases Deployment overview Conﬂicts as they occur Resolve update conﬂicts are all easy to doTest before deployment Changes to avoid on a running systemPage Mixed operating systems and database extraction Synchronizing databasesExample To create a remote database from the reload ﬁle Using the extraction utilityWhere path is the path of the reload command ﬁle 191 Creating a database from the reload ﬁlesBefore extracting a database Using the extraction utility from Sybase CentralTo extract a database for a remote user Sybase Central Designing an efﬁcient extraction procedureAn efﬁcient approach to extracting many databases Extracting groups Limits to using the extraction utilityThis setup is illustrated in the following diagram Using the extraction utility for Adaptive Server EnterpriseCustomizing the system tables Synchronizing data over a message system 199 SQL Remote AdministrationManagement overview Granting and revoking Publish permissions Managing SQL Remote permissions202 To create a new user as the publisher Sybase CentralTo make an existing user the publisher Sybase Central To revoke Publish permissions Sybase CentralExec sppublisher ’SBeaulieu’ go Granting Remote permissions Granting and revoking Remote and Consolidate permissionsSend messages to e-mail address sbeaulieu@acme.com To make an existing user remote Sybase CentralFollowing options Use an Smtp e-mail systemSelecting a send frequency Agent is run Permissions to user hquser, using the ﬁle message linkGranting Consolidate permissions Statement is executed automatically at the remote databasePermission from user SBeaulieu Assigning permissions in multi-tier installationsTo revoke Remote permissions Sybase Central Publish Working with message types Using message typesTo alter a message type Sybase Central Using Sybase Central to work with message typesTo add a message type Sybase Central Create Remote Message Type type-nameADDRESS address-string Using commands to work with message typesTo drop a message type Sybase Central To create a message type SQL213 To alter a message type SQLTo drop a message type SQL Create Remote Message Type statement onTo set a message control parameter Adaptive Server Anywhere Setting message type control parameters215 By using the ﬁle message systemﬁle message system Ftp message system Troubleshooting ftp problems 218 Smtp message systemMote messages SQL Remote Administration Supported operating systems on Mapi message systemSharing SMTP/POP addresses VIM message system VIM message control parameters Enterprise works on Running the Message AgentMessage Agent batch and continuous modes Names are ssremote and dbremote, respectivelyConnections used by the Message Agent Replication system recovery proceduresTo run the Message Agent in continuous mode To run the Message Agent in batch modeManagement on Ensuring consistent Message Agent settingsSee the sections Transaction log and backup management on Adaptive Server Enterprise transaction log and backupMessage Agent and replication security Troubleshooting errors at remote sitesFor more information, see The Message Agent on Execute the following command against the remote databaseTo conﬁgure a consolidated site to receive log information Use either the -roor the -rtMessage Agent optionTuning throughput by controlling Message Agent threading Tuning Message Agent performanceTuning throughput by caching messages Polling interval Tuning incoming message polling231 Requesting resendsExample Tuning the message sending process Resending messages To those when tuning the incoming-message polling frequencyYour choices dictate how often updates are sent to When a remote user requests that a message beDbremote -ru 1h Encoding scheme Encoding and compressing messagesCreating custom encoding schemes Tracking messages by transaction log offsets Message tracking systemStatus information in the remoteuser table Transaction log Agent -loption to change this settingAre offsets in the local database transaction log, Cannot be a later offset than logsentIts resendcount Handling of lost or corrupt messagesPage 241 Administering SQL Remote for Adaptive Server AnywhereStarting the Message Agent Running the Message Agent as a serviceDBA authority grants them no extra permissions Full DBA permissions from the Message Agent When connectingFull DBA permissions on the database Suggested practice is to grant Remote DBA authority atPage Agent output Error reporting and handlingDefault error handling Ignoring errors246 Implementing error handling proceduresExample e-mailing notiﬁcation of errors Following stored procedure implements this notiﬁcationCommit Work Columns have the following meaning 247248 Here is a sample insert into the table from the above errorSetting the transaction log directory Transaction log and backup managementSuch a directory is kept in proper shape Backup utility optionsUsing the live directory as the transaction log directory Using the backup directory as the transaction log directory Following command line252 Managing old transaction logs 254 Recovery with a single transaction logTo recover the database Recovery with multiple transaction logs To recover from media failure on the C driveBackup the mirrored transaction log d\mirdir\consol.mlg Start the database using the following command lineMake a copy of the database and log ﬁle Backups daily using the following commandCommand line would be Backup the mirrored transaction log d\mirdir\cons.mlgRestart your system as normal Backup procedures at remote databasesApply the renamed transaction logs in order, as follows 258 Upgrading consolidated databasesTo unload and reload a consolidated database manual Using passthrough mode Uses and limitations of passthrough mode However, the following dynamic SQL statement is replicated Operations not replicated in passthrough modeOn a running SQL Remote setup Procedure on the replicate side has the correct effect263 Administering SQL Remote for Adaptive Server EnterpriseMessage Agent on How the Message Agent for Adaptive Server Enterprise worksScanning the transaction log Stable queue Administering SQL Remote for Adaptive Server Enterprise266 Message Agent operation phases267 TransactionStable Logqueue Message Agent268 Running multiple Message Agents For setup instructions, see Setting Up SQL Remote onTo execute Agent output Protecting against media failure on the transaction log Transaction log management Stable queue recovery issues274 With the following commandTruncation point can be reset with the following command Freed by Dump TransactionMaking schema changes Schema modiﬁcations 277 Using SQL Remote with Replication ServerWhen you need to use the SQL Remote Open Server How the pieces ﬁt together Architecture for Replication Server/SQL Remote installationsMessage system Stable Queue Agent On Windows operating systems, the SQL Remote Open Server is Information to retrieve it when it startsRemote Open Server on SQL Remote Open Server is the following executableAdd the SQL Remote Open Server to the setup This stage is Setting up SQL Remote Open ServerSame regardless of previous installations To set up the SQL Remote Open Server Page Create replication deﬁnitions for SQL Remote data Conﬁguring Replication ServerSet the dsixactgroupsize parameter Set the dsinumthreads parameterSuspend and restart the connection Other issues 288 This part presents reference material for SQL Remote Page 291 Utilities and Options ReferenceDbremote ssremote options directory Message AgentTracking system to ensure message delivery Utilities and Options Reference Replication security on Listing, see Connections used by the Message Agent on295 Languagename,charsetname,sortorder For more information, see Running multiple Message Agents on Page Dbremote -rd 30s Page NetWare Registry, at the following locationYou should create a ﬁle named dbremote.ini WindowsExtracting a remote database in Sybase Central Database Extraction utility303 Extraction utility304 Remote Adaptive Server Anywhere database Extraction utility options Utilities and Options Reference Optional Database name. If this parameter is not sup 309 Page Input SQL Remote Open Server Server Enterprise and Adaptive Server Anywhere databasesName of the executable is as follows Default value for the open server name is SSQueueGain access to the SQL Remote system tables Values default to the -cvaluesPage SQL Remote options Page Yy yyyy mm mmm dd Hh nn mm Ss.s 318Relationships on Sphookdbremoteend and sphookssrmtend SQL Remote event-hook proceduresSphookdbremotebegin and sphookssrmtbegin Sphookdbremotereceiveend and sphookssrmtreceiveend Sphookdbremoteshutdown and sphookssrmtshutdownSphookdbremotereceivebegin and sphookssrmtreceivebegin Sphookdbremotemessagemissing and sphookssrmtmessagemissing Sphookdbremotesendbegin and sphookssrmtsendbeginSphookdbremotesendend and sphookssrmtsendend Sphookdbremotemessagesent and sphookssrmtmessagesent323 Has applied a set of messages from a userPage 325 System Objects for Adaptive Server AnywhereEach row describes an article in a SQL Remote publication SQL Remote system tablesSysarticle table 327 Sysarticlecol tableIt is in, and the publication it is part Each row describes a SQL Remote publication Syspublication tableSysremoteoption table Sysremoteoptiontype table329 Sysremotetype tableSysremoteuser table Publisher addressConsolidate 330331 Syssubscription tableRemote permissions to one publication 332 Syspublications view SQL Remote system viewsSysarticles view Sysarticlecols viewSysremoteusers view Sysremoteoptions view335 Syssubscriptions viewEach row lists information about a subscription 336 337 System Objects for Adaptive Server EnterpriseTable has a single row #remote tableSrarticle table Manage SQL Remote information339 Srarticlecol tableSrmarker table Databases in the same sessionEach row describes a replication option used by SQL Remote Srobject tableSroption table Srpassthrough tableSrremoteoption table Srpublication tableSrpublisher table 342 Srremoteoptiontype tableSrremotetable table Srremotetype table343 Srremoteuser tableReceived 344345 Srsubscription tableSrpublications view Srarticles viewSrarticlecols view Srremotetypes view Srremoteoptions viewSrremotetables view 348 Srremoteusers view349 Srsubscriptions view350 Stable Queue tablesSrqueuestate table Stable queue351 Srtransaction table352 Srconﬁrmedtransaction tableSrqueuecoordinate table Each row marks the corresponding row in srtransaction353 Command Reference for Adaptive Server Anywhere354 Automatic commit Alter Remote Message Type statementBeen created Must have DBA authoritySubscribe by expression Create Publication statementCreate Publication statement ASA SQL Reference, Create Remote Message Type message-system Create Remote Message Type statementMessages from a database Create Remote Message Type statement SQL Remote ASA SQLCreate Subscription statement SQL Remote ASA SQL Reference Create Subscription statementCreate Trigger statement Create Trigger statement SQL Remote ASA SQL Reference Update statement onMust have Resource authority and have Alter permissions on Table and thus requires exclusive use of the tableDrop Publication statement ASA SQL Reference, Drop Publication statementDrop Remote Message Type message-system Drop Remote Message Type statementGranted Remote or Consolidate permissions with this type Drop Remote Message Type statement SQL Remote ASA SQLDrop Subscription statement SQL Remote ASA SQL Reference Drop Subscription statementSend Every AT ’hhmm ss’ Grant Consolidate statementCurrent database Grant Consolidate statement SQL Remote ASA SQL ReferenceGrant Publish statement Grant Remote statement Grant Remote DBA statement SQL Remote ASA SQL Reference Identified by passwordGrant Remote DBA statement Connected from the Message AgentPassthrough statement SQL Remote ASA SQL Reference, Passthrough modeSppassthrough procedure on Passthrough statementNo automatic commit is done by this statement Remote Reset statementRemote Reset statement SQL Remote ASA SQL Reference, Subscriptions for a remote user in a single transactionAutomatic commit. Drops all subscriptions for the user Sprevokeconsolidate procedure onRevoke Consolidate statement SQL Remote messages from this databaseRevoke Publish from userid Revoke Publish statementCurrent publisher Revoke Publish statement SQL Remote ASA SQL ReferenceRevoke Remote statement SQL Remote ASA SQL Reference Sprevokeremote procedure onRevoke Remote statement Messages from this databaseRevoke Remote DBA statement SQL Remote ASA SQL Reference Revoke Remote DBA statementMessage link Splinkoption procedure onSET Remote Option statement Start Subscription Start Subscription statementStop Subscription Stop Subscription statementSynchronize Subscription Synchronize Subscription statementCreate Trigger statement on Update statementUpdate statement SQL Remote ASA SQL Reference, 379 Command Reference for Adaptive Server Enterprise380 Spaddarticle procedure 382 Making schema changes onSalesRepData Spaddarticlecol publicationname Spaddarticlecol procedureTo add a column to an article in a publication To mark a table for SQL Remote replication Spaddremotetable procedure385 Default conﬂict resolutionRemote rows are stored in tables named oldCustomer RemoteCustomer, respectivelySpcreatepublication publicationname Spcreatepublication procedureSpdroppublication procedure on To create a publicationSpdroppublication publicationname Spdroppublication procedureSpcreatepublication procedure on To drop a publication from the databaseSpdropremotetype typename Spdropremotetype procedureProcedure on Spdropsqlremote procedureSpqueuedrop procedure on Databases acting as remote databases Spgrantconsolidate procedureSee also Description Example 392 Spgrantremote procedure Speciﬁed Current database must be granted Remote permissions usingSingle quotes One of the publications in the current database395 Databases Splinkoption procedureSET Remote Option statement on Smtp message system on ﬁle message system onFtp message system on Mapi message system onTo change the description of an article in a procedure Spmodifyarticle procedure399 Subscription expressionExpression that is the repkey column Managing conﬂicts on Spmodifyremotetable procedureSpaddremotetable procedure on Spremoveremotetable procedure on401 Sppassthrough procedure Sppassthroughpiece string Sppassthroughpiece procedureTo build a long SQL statement for passthrough 404 Currently being built Sppassthroughstop procedureResents passthrough mode Sppassthroughstop procedure resents the list of recipientsSppassthroughsubscription publicationname Sppassthroughsubscription procedureStatements Sppassthroughuser username Sppassthroughuser procedureSppopulatesqlanywhere Sppopulatesqlanywhere procedureConsolidated database Called directlySppublisher username Sppublisher procedureLog was scanned Spqueueclean procedureSpqueueclean Be called directlySpqueueconﬁrmeddeleteold Spqueueconﬁrmeddeleteold procedureSpqueueconﬁrmedtransaction offset Spqueueconﬁrmedtransaction procedureMatch this offset Spqueuedeleteold Spqueuedeleteold procedureBeen conﬁrmed by all remote databases Spdropsqlremote procedure on Spqueuedrop procedureStable queue recovery issues on Spqueuedumpdatabase procedureSpqueuedumptransaction procedure on Spqueuedumptransaction Spqueuedumptransaction procedureSpqueuedumpdatabase procedure on Spqueuegetstate Spqueuegetstate procedureQueue Spqueuelogtransferreset Spqueuelogtransferreset procedureBe called directly. It resets the page and row IDs to zero Spqueueread startoffset Spqueueread procedureUse by the Message Agent Spqueuereset Spqueuereset procedureReady for a new SQL Remote setup Spqueuesetconﬁrm conﬁrmoffset Spqueuesetconﬁrm procedureUsers in the srqueuestate table Spqueuesetprogress pageid Spqueuesetprogress procedureSpqueuetransaction offset Spqueuetransaction procedureSpremote operation Spremote procedureMessage tracking information in the srremoteuser table To set a SQL Remote option Spremoteoption procedure426 Alter Remote Message Type statement on Spremotetype procedureSpdropremotetype procedure on Spremovearticle publicationname Spremovearticle procedureSpaddarticle procedure on To remove an article from a publicationSpremovearticlecol publicationname Spremovearticlecol procedureTo remove a column from an article in a publication Spremoveremotetable tablename Spremoveremotetable procedureSpmodifyremotetable procedure on To mark a table as unavailable for SQL Remote replicationSprevokeconsolidate username Sprevokeconsolidate procedureSpgrantconsolidate procedure on Sprevokeremote username Sprevokeremote procedureSpsubscription procedure Srsubscription tables to zero or Null Spsubscriptionreset procedureTo reset all SQL Remote information for all remote users SpsubscriptionresetAppendices Page 437 Types of difference Differences in functionality Differences in approach 441 Limitations for Enterprise to Enterprise replication Page Page 445 Supported Platforms and Message LinksSupported message systems Windows NT/2000/XP All message links Supported operating systems448 Index Symbols450 IndexCurrent Remote User 451Sqlremote 452453 LTM 454455 Subscribebyremote 456Remote 457458 459 Send Every 460461 462 Tempdb 463464 465 466 Unix 467