Manuals / Sybase / Personal Care / Microscope & Magnifier

Sybase DC38133-01-0902-01 manual Message Agent operation phases, 266

Models: DC38133-01-0902-01

1 485

Download 485 pages 33.95 Kb

Page 284

Do not modify the stable queue directly

The stable queue is maintained by and for the Message Agent. You should not modify the stable queue directly.

The stable queue consists of a set of tables that contain information on all transactions scanned from the transaction log,

☞For a description of each of the columns of these tables, see “Stable Queue tables” on page 350 .

Message Agent operation phases

The Message Agent has the following phases of execution:

♦Receiving messages During this phase, the Message Agent receives incoming messages and applies them to the Adaptive Server Enterprise server.

Message system

Message

Agent

♦Populating the stable queue During this phase the Message Agent scans the Adaptive Server Enterprise transaction log into the stable queue.

266

Image 284

Sybase DC38133-01-0902-01 manual Message Agent operation phases, 266

Contents

SQL Remote User’s Guide Part number DC38133-01-0902-01 Last modiﬁed OctoberPage Contents SQL Remote Administration 199 Principles of SQL Remote DesignSQL Remote Design for Adaptive Server Anywhere SQL Remote Design for Adaptive Server Enterprise 141Administering SQL Remote for Adaptive Server Anywhere241 Using SQL Remote with Replication Server 277System Objects for Adaptive Server Anywhere 325 Utilities and Options Reference 291Command Reference for Adaptive Server Anywhere 353 Command Reference for Adaptive Server Enterprise 379Server Anywhere Differences 437 SQL Remote for Adaptive Server Enterprise and AdaptiveSupported Platforms and Message Links 445 Index 449Viii Systems About This ManualMail or ﬁle transfer SQL Anywhere Studio documentation Adaptive Server Anywhere Database Administration Guide ThisPage Page Documentation conventions Release Savepoint savepoint-nameFollowing icons are used in this documentation Client applicationDatabase server, such as Sybase Adaptive Server Anywhere XivAdaptive Server Anywhere sample database Asademo.dbFinding out more and providing feedback Page Xviii Introduction to SQL Remote Page Welcome to SQL Remote This chapter introduces SQL Remote and the documentationSQL Remote for Adaptive Server Anywhere Enables replication About SQL RemoteProduct installation To install the SQL Remote software WindowsTo install the SQL Remote software Unix About this manualPage SQL Remote Concepts SQL RemoteSQL Remote components Message Agent Data serverClient applications Message system client Publications and subscriptions Two-table synchronization definitionReplication At the remote databaseSQL Remote features Page Some sample installations Server-to-laptop replication for mobile workforcesServer-to-server replication among ofﬁces More Page Setting Up SQL Remote Setup overview Each user in the installationSybase System Administrator should perform all SQL Remote You must take some steps toInstalling the SQL Remote system objects To install the SQL Remote system objectsPreparing your Adaptive Server Enterprise server Ensuring Tempdb is large enoughSQL Remote system objects Command-line installation of the stable queue To install the stable queuePage To upgrade SQL Remote Upgrading SQL Remote for Adaptive Server EnterpriseTo uninstall the stable queue from a database Uninstalling SQL RemoteTo uninstall the SQL Remote objects from a database Tutorials for Adaptive Server Anywhere Users Just on those issues important for replication IntroductionGoals DatabaseTutorials for Adaptive Server Anywhere Users Tables are described in more detail as followsReplication goals RepkeyName CustkeySybase Central or command-line utilities Preparing for the Sybase Central replication tutorial To prepare for the tutorialTo add tables to the consolidated database Setting up a consolidated database Add a SQL Remote message typeTo add an address to a message type Add the publisher and remote user to the databaseTo create a new user as the publisher To add a publication To add a remote userAdd publications and subscriptions Set up the remote database in Sybase Central Enter the expression repkeyClick Finish to create the publication Publication for the remote database user ﬁelduserTo extract a database Preparing for the replication tutorial To create the databases and directories for the 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 Start replicating data Enter data at the consolidated databaseSend data from the consolidated database First, enter some data into the consolidated databaseTo receive data at the remote database Receive data at the remote databaseTo send the data to the remote database To verify that the data has arrived Commit the insertion by executing the following statementCustkey Name Repkey Sample publication To add the publication to the sample databasePage Tutorial for Adaptive Server Enterprise Users Database schema for the tutorial is illustrated in the ﬁgure Tutorial for Adaptive Server Enterprise Users SalesRep table is many-to-onePage Tutorial Adaptive Server Enterprise replication First stepsTo 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 message links and addresses Create the necessary users and permissionsTo create the publisher To create the subscriberCreate the publication and subscription Create an empty publicationTo create a subscription Create a subscription to SalesRepData for ﬁelduser , with aSubscription value of rep1 Extract the remote databaseTo 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 To enter data at the Adaptive Server Enterprise database Connect to the Adaptive Server Enterprise server from isqlTo replicate the data from Adaptive Server Enterprise To receive the data at Adaptive Server AnywhereCommit the row Custkey Name Repkey Page Replication Design for SQL Remote Page Principles of SQL Remote Design Adaptive Server Enterprise System Administrator or database Design overviewEnsuring compatible databases SQL Remote replicates dataUsing compatible sort orders and character sets SQL Remote Message Agent does not perform any character setConversions Between Ssremote and Adaptive Server Enterprise whenever819LATIN1 Eucjapan Replication of inserts and deletes Replication of updatesHow statements are replicated Clause of the Update statement User, the row to be updated is not foundStatement RepresentativesReplication of procedures This case, the Update does not update anythingProcedure call is not replicated Replication of triggersMessage causing the conﬂict Body of your triggersActions carried out by conﬂict Some Before triggers can produceReplication of data deﬁnition statements How data types are replicated Replication of blobsReplication of dates and times Select Who gets what? Principles of SQL Remote Design Replication conﬂicts Replication errors and conﬂictsReplication errors Tracking SQL errors Issue the following statementVARCHAR, or Long VARCHAR. The procedure is called once with DetectedPage SQL Remote Design for Adaptive Server Anywhere Publications determine what information Is shared among which databasesSubscriptions determine what Information each user receivesPublishing data Publishing whole tablesTo publish one or more entire tables Sybase Central To publish one or more entire tables SQLTo publish only some columns in a table Sybase Central Publishing only some columns in a tableFor more information, see the Create Publication statement Publishing only some rows in a table To publish only some columns in a table SQLTo 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 To create an article using a subscription expression SQL ColumnAltering existing publications To add articles Sybase CentralTo 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 Design issues overview Publication design for Adaptive Server AnywhereConditions for valid articles Design tips for performancePay 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 Reps Properly transferred to the new sales representativeAlong with the Customer For which there is no longer a CustomerSpecial Update statement for publications Understanding this helps in designing efﬁcient publications Assume the following data∙ SalesRep table ∙ Customer tableSalesRepData Publication Name rep1 Before list Many-to-many relationship in the database Sharing rows among several subscriptionsPolicy example With the following information Entire SalesRep tableInvolving the sales rep subscribed to the data 113Publication Territory realignment with a many-to-many relationship Contact example onRemote databases contain the proper data 116Customer being transferred Where custkey = OldRow.custkey That this subquery can be multi-valuedCan be multi-valued Dealing with the customer, taken from the Policy tableCustomer SQL Remote Design for Adaptive Server Anywhere Managing conﬂicts ID Rep Dept Ann MarcMust be excluded from the installation by proper design SQL Remote installation at the consolidated databaseHow SQL Remote handles conﬂicts UpdatingImplementing conﬂict resolution Using conﬂict resolution triggersCreate Trigger trigger-name Referencing OLD AS oldvalConﬂict resolution examples Resolving date conﬂictsResolving inventory conﬂicts Increments from the two updates. For example Reporting conﬂictsIncludes the salesorder table Designing to avoid referential integrity errorsDesigning triggers to avoid errors Page Using global autoincrement default column values Ensuring unique primary keysDeclaring default global autoincrement Setting the Globaldatabaseid valueDatabase 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 136 Cursor forAdding new customers ElsePrimary key pool summary InsertCreating subscriptions To create and manage subscriptions in Sybase CentralFor more information, see Create Subscription statement on 140SQL Remote Design for Adaptive Server Enterprise 141Design 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 To handle this case, using an example Contain the subscription columnTwo tables described earlier in this chapter 149150 Are realigned Adding a subscription-list column to the Contact table Exec spcreatepublication ’SalesRepData’ goLog entries are values, not subscribers Update on the Contact table Update on the Customer tableMaintaining the subscription-list column For the following operationsTuning extraction performance SQL Remote Design for Adaptive Server Enterprise156 To create a subscription viewCreate a view that contains this subquery. For example Solving the problem 158 Foreign KEY159 Subscriptions to this publication take the following formThese objects Triggers 161 For Insert AS BeginTuning extraction performance for shared rows Ensure the quotedidentiﬁer option is set to on163 Customer Managing conﬂicts Consolidated database, no row will be updated Any conﬂict resolution procedures are calledDatabase objects to handle the resolution When the conﬂicting message arrivedNames of the conﬂict resolution objects Remoterowtable. These three are discussed in turnTable only ever contains a single row This table must have the same column names168 ﬁrst conﬂict resolution exampleTwo-table database is as follows Conﬂict-causing Update After the procedure is run, the rows in the OldCustomerFollows @lostname value is the value that was overridden byConﬂictLog table has a single row, showing the conﬂict Second conﬂict resolution exampleTo test the example It when the procedure is executed Lost and won namesUser ID of the remote user. The table is as follows Replaces it with the value that was previously presentWhere conﬂict resolution is carried out by Before triggers There are several points of note hereUser ID of the remote user is stored by the Message Agent Currentremoteuser column of the temporary table #remote173 Page Primary key pool Columns of this table have the following meanings 175To replicate the primary key pool 176177 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 Resolve update conﬂicts are all easy to do Test before deploymentChanges to avoid on a running system Conﬂicts as they occurPage Synchronizing databases Mixed operating systems and database extractionExample Using the extraction utility Where path is the path of the reload command ﬁle 191Creating a database from the reload ﬁles To create a remote database from the reload ﬁleUsing the extraction utility from Sybase Central Before extracting a databaseDesigning an efﬁcient extraction procedure To extract a database for a remote user Sybase CentralAn efﬁcient approach to extracting many databases Limits to using the extraction utility Extracting groupsUsing the extraction utility for Adaptive Server Enterprise This setup is illustrated in the following diagramCustomizing the system tables Synchronizing data over a message system SQL Remote Administration 199Management overview Managing SQL Remote permissions Granting and revoking Publish permissionsTo create a new user as the publisher Sybase Central To make an existing user the publisher Sybase CentralTo revoke Publish permissions Sybase Central 202Exec sppublisher ’SBeaulieu’ go Granting and revoking Remote and Consolidate permissions Granting Remote permissionsTo make an existing user remote Sybase Central Following optionsUse an Smtp e-mail system Send messages to e-mail address sbeaulieu@acme.comSelecting a send frequency Permissions to user hquser, using the ﬁle message link Granting Consolidate permissionsStatement is executed automatically at the remote database Agent is runPermission from user SBeaulieu Assigning permissions in multi-tier installationsTo revoke Remote permissions Sybase Central Publish Using message types Working with message typesTo alter a message type Sybase Central Using Sybase Central to work with message typesTo add a message type Sybase Central Using commands to work with message types To drop a message type Sybase CentralTo create a message type SQL Create Remote Message Type type-nameADDRESS address-stringTo alter a message type SQL To drop a message type SQLCreate Remote Message Type statement on 213Setting message type control parameters To set a message control parameter Adaptive Server Anywhere215 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 Running the Message Agent Message Agent batch and continuous modesNames are ssremote and dbremote, respectively Enterprise works onReplication system recovery procedures To run the Message Agent in continuous modeTo run the Message Agent in batch mode Connections used by the Message AgentEnsuring consistent Message Agent settings See the sections Transaction log and backup management onAdaptive Server Enterprise transaction log and backup Management onTroubleshooting errors at remote sites Message Agent and replication securityExecute the following command against the remote database To conﬁgure a consolidated site to receive log informationUse either the -roor the -rtMessage Agent option For more information, see The Message Agent onTuning Message Agent performance Tuning throughput by controlling Message Agent threadingTuning throughput by caching messages Tuning incoming message polling Polling interval231 Requesting resendsExample Tuning the message sending process To those when tuning the incoming-message polling frequency Your choices dictate how often updates are sent toWhen a remote user requests that a message be Resending messagesDbremote -ru 1h Encoding and compressing messages Encoding schemeCreating custom encoding schemes Tracking messages by transaction log offsets Message tracking systemStatus information in the remoteuser table Agent -loption to change this setting Are offsets in the local database transaction log,Cannot be a later offset than logsent Transaction logHandling of lost or corrupt messages Its resendcountPage Administering SQL Remote for Adaptive Server Anywhere 241Running the Message Agent as a service Starting the Message AgentFull DBA permissions from the Message Agent When connecting Full DBA permissions on the databaseSuggested practice is to grant Remote DBA authority at DBA authority grants them no extra permissionsPage Error reporting and handling Default error handlingIgnoring errors Agent outputImplementing error handling procedures Example e-mailing notiﬁcation of errorsFollowing stored procedure implements this notiﬁcation 246Columns have the following meaning 247 Commit WorkHere is a sample insert into the table from the above error 248Transaction log and backup management Setting the transaction log directorySuch a directory is kept in proper shape Backup utility optionsUsing the live directory as the transaction log directory Following command line Using the backup directory as the transaction log directory252 Managing old transaction logs 254 Recovery with a single transaction logTo recover the database To recover from media failure on the C drive Backup the mirrored transaction log d\mirdir\consol.mlgStart the database using the following command line Recovery with multiple transaction logsBackups daily using the following command Command line would beBackup the mirrored transaction log d\mirdir\cons.mlg Make a copy of the database and log ﬁleRestart your system as normal Backup procedures at remote databasesApply the renamed transaction logs in order, as follows Upgrading consolidated databases 258To unload and reload a consolidated database manual Using passthrough mode Uses and limitations of passthrough mode Operations not replicated in passthrough mode On a running SQL Remote setupProcedure on the replicate side has the correct effect However, the following dynamic SQL statement is replicatedAdministering SQL Remote for Adaptive Server Enterprise 263Message Agent on How the Message Agent for Adaptive Server Enterprise worksScanning the transaction log Administering SQL Remote for Adaptive Server Enterprise Stable queueMessage Agent operation phases 266TransactionStable Logqueue Message Agent 267268 For setup instructions, see Setting Up SQL Remote on Running multiple Message AgentsTo execute Agent output Protecting against media failure on the transaction log Stable queue recovery issues Transaction log managementWith the following command Truncation point can be reset with the following commandFreed by Dump Transaction 274Making schema changes Schema modiﬁcations Using SQL Remote with Replication Server 277When you need to use the SQL Remote Open Server Architecture for Replication Server/SQL Remote installations How the pieces ﬁt togetherMessage system Stable Queue Agent Information to retrieve it when it starts Remote Open Server onSQL Remote Open Server is the following executable On Windows operating systems, the SQL Remote Open Server isAdd 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 Conﬁguring Replication Server Set the dsixactgroupsize parameterSet the dsinumthreads parameter Create replication deﬁnitions for SQL Remote dataSuspend and restart the connection Other issues 288 This part presents reference material for SQL Remote Page Utilities and Options Reference 291Dbremote ssremote options directory Message AgentTracking system to ensure message delivery Utilities and Options Reference Listing, see Connections used by the Message Agent on Replication security on295 Languagename,charsetname,sortorder For more information, see Running multiple Message Agents on Page Dbremote -rd 30s Page Registry, at the following location You should create a ﬁle named dbremote.iniWindows NetWareDatabase Extraction utility Extracting a remote database in Sybase CentralExtraction utility 303304 Remote Adaptive Server Anywhere database Extraction utility options Utilities and Options Reference Optional Database name. If this parameter is not sup 309 Page Input Server Enterprise and Adaptive Server Anywhere databases SQL Remote Open ServerDefault value for the open server name is SSQueue Gain access to the SQL Remote system tablesValues default to the -cvalues Name of the executable is as followsPage SQL Remote options Page Yy yyyy mm mmm dd 318 Hh nn mm Ss.sRelationships on Sphookdbremoteend and sphookssrmtend SQL Remote event-hook proceduresSphookdbremotebegin and sphookssrmtbegin Sphookdbremotereceiveend and sphookssrmtreceiveend Sphookdbremoteshutdown and sphookssrmtshutdownSphookdbremotereceivebegin and sphookssrmtreceivebegin Sphookdbremotesendbegin and sphookssrmtsendbegin Sphookdbremotesendend and sphookssrmtsendendSphookdbremotemessagesent and sphookssrmtmessagesent Sphookdbremotemessagemissing and sphookssrmtmessagemissingHas applied a set of messages from a user 323Page System Objects for Adaptive Server Anywhere 325Each 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 Syspublication table Sysremoteoption tableSysremoteoptiontype table Each row describes a SQL Remote publicationSysremotetype table Sysremoteuser tablePublisher address 329330 Consolidate331 Syssubscription tableRemote permissions to one publication 332 SQL Remote system views Sysarticles viewSysarticlecols view Syspublications viewSysremoteoptions view Sysremoteusers view335 Syssubscriptions viewEach row lists information about a subscription 336 System Objects for Adaptive Server Enterprise 337#remote table Srarticle tableManage SQL Remote information Table has a single rowSrarticlecol table Srmarker tableDatabases in the same session 339Srobject table Sroption tableSrpassthrough table Each row describes a replication option used by SQL RemoteSrremoteoption table Srpublication tableSrpublisher table Srremoteoptiontype table Srremotetable tableSrremotetype table 342Srremoteuser table 343344 ReceivedSrsubscription table 345Srpublications view Srarticles viewSrarticlecols view Srremotetypes view Srremoteoptions viewSrremotetables view Srremoteusers view 348Srsubscriptions view 349Stable Queue tables Srqueuestate tableStable queue 350Srtransaction table 351Srconﬁrmedtransaction table Srqueuecoordinate tableEach row marks the corresponding row in srtransaction 352Command Reference for Adaptive Server Anywhere 353354 Alter Remote Message Type statement Been createdMust have DBA authority Automatic commitSubscribe by expression Create Publication statementCreate Publication statement ASA SQL Reference, Create Remote Message Type statement Messages from a databaseCreate Remote Message Type statement SQL Remote ASA SQL Create Remote Message Type message-systemCreate Subscription statement Create Subscription statement SQL Remote ASA SQL ReferenceCreate Trigger statement Update statement on Must have Resource authority and have Alter permissions onTable and thus requires exclusive use of the table Create Trigger statement SQL Remote ASA SQL ReferenceDrop Publication statement Drop Publication statement ASA SQL Reference,Drop Remote Message Type statement Granted Remote or Consolidate permissions with this typeDrop Remote Message Type statement SQL Remote ASA SQL Drop Remote Message Type message-systemDrop Subscription statement Drop Subscription statement SQL Remote ASA SQL ReferenceGrant Consolidate statement Current databaseGrant Consolidate statement SQL Remote ASA SQL Reference Send Every AT ’hhmm ss’Grant Publish statement Grant Remote statement Identified by password Grant Remote DBA statementConnected from the Message Agent Grant Remote DBA statement SQL Remote ASA SQL ReferencePassthrough mode Sppassthrough procedure onPassthrough statement Passthrough statement SQL Remote ASA SQL Reference,Remote Reset statement Remote Reset statement SQL Remote ASA SQL Reference,Subscriptions for a remote user in a single transaction No automatic commit is done by this statementSprevokeconsolidate procedure on Revoke Consolidate statementSQL Remote messages from this database Automatic commit. Drops all subscriptions for the userRevoke Publish statement Current publisherRevoke Publish statement SQL Remote ASA SQL Reference Revoke Publish from useridSprevokeremote procedure on Revoke Remote statementMessages from this database Revoke Remote statement SQL Remote ASA SQL ReferenceRevoke Remote DBA statement Revoke Remote DBA statement SQL Remote ASA SQL ReferenceMessage link Splinkoption procedure onSET Remote Option statement Start Subscription statement Start SubscriptionStop Subscription statement Stop SubscriptionSynchronize Subscription statement Synchronize SubscriptionCreate Trigger statement on Update statementUpdate statement SQL Remote ASA SQL Reference, Command Reference for Adaptive Server Enterprise 379380 Spaddarticle procedure 382 Making schema changes onSalesRepData Spaddarticlecol publicationname Spaddarticlecol procedureTo add a column to an article in a publication Spaddremotetable procedure To mark a table for SQL Remote replicationDefault conﬂict resolution Remote rows are stored in tables named oldCustomerRemoteCustomer, respectively 385Spcreatepublication procedure Spdroppublication procedure onTo create a publication Spcreatepublication publicationnameSpdroppublication procedure Spcreatepublication procedure onTo drop a publication from the database Spdroppublication publicationnameSpdropremotetype procedure Spdropremotetype typenameProcedure on Spdropsqlremote procedureSpqueuedrop procedure on Spgrantconsolidate procedure Databases acting as remote databasesSee also Description Example 392 Spgrantremote procedure Current database must be granted Remote permissions using Single quotesOne of the publications in the current database Speciﬁed395 Databases Splinkoption procedureSET Remote Option statement on ﬁle message system on Ftp message system onMapi message system on Smtp message system onSpmodifyarticle procedure To change the description of an article in a procedure399 Subscription expressionExpression that is the repkey column Spmodifyremotetable procedure Spaddremotetable procedure onSpremoveremotetable procedure on Managing conﬂicts on401 Sppassthrough procedure Sppassthroughpiece string Sppassthroughpiece procedureTo build a long SQL statement for passthrough 404 Sppassthroughstop procedure Resents passthrough modeSppassthroughstop procedure resents the list of recipients Currently being builtSppassthroughsubscription publicationname Sppassthroughsubscription procedureStatements Sppassthroughuser procedure Sppassthroughuser usernameSppopulatesqlanywhere procedure Consolidated databaseCalled directly SppopulatesqlanywhereSppublisher procedure Sppublisher usernameSpqueueclean procedure SpqueuecleanBe called directly Log was scannedSpqueueconﬁrmeddeleteold procedure SpqueueconﬁrmeddeleteoldSpqueueconﬁrmedtransaction offset Spqueueconﬁrmedtransaction procedureMatch this offset Spqueuedeleteold Spqueuedeleteold procedureBeen conﬁrmed by all remote databases Spqueuedrop procedure Spdropsqlremote procedure onStable 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 procedure Spqueuesetprogress pageidSpqueuetransaction procedure Spqueuetransaction offsetSpremote operation Spremote procedureMessage tracking information in the srremoteuser table Spremoteoption procedure To set a SQL Remote option426 Alter Remote Message Type statement on Spremotetype procedureSpdropremotetype procedure on Spremovearticle procedure Spaddarticle procedure onTo remove an article from a publication Spremovearticle publicationnameSpremovearticlecol publicationname Spremovearticlecol procedureTo remove a column from an article in a publication Spremoveremotetable procedure Spmodifyremotetable procedure onTo mark a table as unavailable for SQL Remote replication Spremoveremotetable tablenameSprevokeconsolidate username Sprevokeconsolidate procedureSpgrantconsolidate procedure on Sprevokeremote procedure Sprevokeremote usernameSpsubscription procedure Spsubscriptionreset procedure To reset all SQL Remote information for all remote usersSpsubscriptionreset Srsubscription tables to zero or NullAppendices Page 437 Types of difference Differences in functionality Differences in approach 441 Limitations for Enterprise to Enterprise replication Page Page Supported Platforms and Message Links 445Supported message systems Supported operating systems Windows NT/2000/XP All message links448 Symbols IndexIndex 450451 Current Remote User452 Sqlremote453 454 LTM455 456 Subscribebyremote457 Remote458 459 460 Send Every461 462 463 Tempdb464 465 466 467 Unix