Ftp message system | Sybase DC38133-01-0902-01 guide

FILE message control parameters

You can also use the ﬁle system to put the messages in directories on the consolidated and remote machines. A simple ﬁle transfer mechanism can then be used to exchange the ﬁles periodically to effect replication.

The FILE message system uses the following control parameters:

♦Directory This is set to the directory under which the messages are stored. The setting is an alternative to the SQLREMOTE environment variable.

♦Debug This is set to either YES or NO, with the default being NO. When set to YES, all ﬁle system calls made by the FILE link are displayed.

♦Unlink_delay This is the number of seconds to wait before attempting to delete a ﬁle if the previous attempt to delete the ﬁle failed. If no value is deﬁned for unlink_delay, then the default behavior is to pause for 1 second after the ﬁrst failed attempt, 2 seconds after the second failed attempt, 3 seconds after the third failed attempt, and 4 seconds after the fourth failed attempt.

On NetWare, you should create a ﬁle named dbremote.ini in the sys:\system directory to hold the directory setting.

The ftp message system

Addresses for ftp

FTP message control parameters

In the ftp message system, messages are stored in directories under a root directory on an ftp host. The ftp host and the root directory are speciﬁed by message system control parameters held in the registry or initialization ﬁle, and the address of each user is the subdirectory where their messages are held.

☞For a list of operating systems for which ftp is supported, see “Supported operating systems” on page 447 .

The ftp message system uses the following control parameters:

♦host The host name of the computer where the messages are stored. This can be a host name (such as ftp.ianywhere.com) or an IP address (such as 192.138.151.66).

♦user The user name for accessing the ftp host.

♦password The password for accessing the ftp host.

♦root_directory The root directory within the ftp host site, under which the messages are stored.

216

Image 234

Sybase DC38133-01-0902-01 manual Ftp message system

Contents

SQL Remote User’s Guide Part number DC38133-01-0902-01 Last modiﬁed OctoberPage Contents SQL Remote Design for Adaptive Server Anywhere SQL Remote Administration 199Principles of SQL Remote Design SQL Remote Design for Adaptive Server Enterprise 141 System Objects for Adaptive Server Anywhere 325 Administering SQL Remote for Adaptive Server Anywhere241Using SQL Remote with Replication Server 277 Utilities and Options Reference 291 Command Reference for Adaptive Server Anywhere 353 Command Reference for Adaptive Server Enterprise 379 Supported Platforms and Message Links 445 Server Anywhere Differences 437SQL Remote for Adaptive Server Enterprise and Adaptive Index 449 Viii About This Manual Mail or ﬁle transferSystems SQL Anywhere Studio documentation Adaptive Server Anywhere Database Administration Guide ThisPage Page Documentation conventions Release Savepoint savepoint-name Database server, such as Sybase Adaptive Server Anywhere Following icons are used in this documentationClient application Xiv Adaptive Server Anywhere sample database Asademo.db Finding out more and providing feedback Page Xviii Introduction to SQL Remote Page Welcome to SQL Remote This chapter introduces SQL Remote and the documentation SQL Remote for Adaptive Server Anywhere Enables replication About SQL Remote To install the SQL Remote software Unix Product installationTo install the SQL Remote software Windows About this manualPage SQL Remote Concepts SQL Remote SQL Remote components Data server Client applicationsMessage Agent Message system client Publications and subscriptions Two-table synchronization definition Replication At the remote database SQL Remote features Page Some sample installations Server-to-laptop replication for mobile workforces Server-to-server replication among ofﬁces More Page Setting Up SQL Remote Sybase System Administrator should perform all SQL Remote Setup overviewEach user in the installation You must take some steps to Preparing your Adaptive Server Enterprise server Installing the SQL Remote system objectsTo install the SQL Remote system objects Ensuring Tempdb is large enough SQL 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 Enterprise Uninstalling SQL Remote To uninstall the SQL Remote objects from a databaseTo uninstall the stable queue from a database Tutorials for Adaptive Server Anywhere Users Goals Just on those issues important for replicationIntroduction Database Tutorials for Adaptive Server Anywhere Users Tables are described in more detail as follows Name Replication goalsRepkey Custkey Sybase Central or command-line utilities Preparing for the Sybase Central replication tutorial To prepare for the tutorial To add tables to the consolidated database Setting up a consolidated database Add a SQL Remote message type To add an address to a message type Add the publisher and remote user to the database To create a new user as the publisher To add a remote user Add publications and subscriptionsTo add a publication Click Finish to create the publication Set up the remote database in Sybase CentralEnter the expression repkey Publication for the remote database user ﬁelduser To extract a database Preparing for the replication tutorial To create the databases and directories for the tutorial Set up the consolidated database To add the tables to the consolidated databaseCreate a SQL Remote message type To create the message type Grant Publish and Remote at the consolidated databaseTo create a publisher for the database Create publications and subscriptions SQL, to create a publicationTable SalesRep, and some of the rows of the table Customer Set up the remote database To create the publicationTo create the subscription Extract the remote database information Load the remote database informationTo load the database information Select * from SalesRep Select * from Customer Send data from the consolidated database Start replicating dataEnter data at the consolidated database First, enter some data into the consolidated database Receive data at the remote database To send the data to the remote databaseTo receive data at the remote database To verify that the data has arrived Commit the insertion by executing the following statement Custkey 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 steps To install SQL Remote into the hq database Setting up the consolidated database Create the SalesRep table with the following statementCreate the Customer table with the following statement Create the message links and addresses Create the necessary users and permissions To create the publisher To create the subscriber Create the publication and subscription Create an empty publication Subscription value of rep1 To create a subscriptionCreate a subscription to SalesRepData for ﬁelduser , with a Extract the remote database To load the data into the database using Interactive SQL Utility onTo create a database ﬁle named ﬁeld.db Connect to the server using the Interactive SQL utility To load the data into the database as a batch processRun the script from Interactive SQL To enter data at the Adaptive Server Enterprise database Connect to the Adaptive Server Enterprise server from isql To replicate the data from Adaptive Server Enterprise To receive the data at Adaptive Server Anywhere Commit the row Custkey Name Repkey Page Replication Design for SQL Remote Page Principles of SQL Remote Design Ensuring compatible databases Adaptive Server Enterprise System Administrator or databaseDesign overview SQL Remote replicates data Conversions Using compatible sort orders and character setsSQL Remote Message Agent does not perform any character set Between Ssremote and Adaptive Server Enterprise whenever 819LATIN1 Eucjapan Replication of updates How statements are replicatedReplication of inserts and deletes Statement Clause of the Update statementUser, the row to be updated is not found Representatives Procedure call is not replicated Replication of proceduresThis case, the Update does not update anything Replication of triggers Actions carried out by conﬂict Message causing the conﬂictBody of your triggers Some Before triggers can produce Replication of data deﬁnition statements How data types are replicated Replication of blobs Replication of dates and times Select Who gets what? Principles of SQL Remote Design Replication errors and conﬂicts Replication errorsReplication conﬂicts VARCHAR, or Long VARCHAR. The procedure is called once with Tracking SQL errorsIssue the following statement DetectedPage SQL Remote Design for Adaptive Server Anywhere Subscriptions determine what Publications determine what informationIs shared among which databases Information each user receives To publish one or more entire tables Sybase Central Publishing dataPublishing whole tables To publish one or more entire tables SQL Publishing only some columns in a table For more information, see the Create Publication statementTo publish only some columns in a table Sybase Central Publishing only some rows in a table To publish only some columns in a table SQL Publishing only some rows using a Where clause To create a publication using a Where clause Sybase CentralTo create a publication using a Where clause SQL Publishing only some rows using a subscription expression To create an article using a subscription expression SQL Column Altering existing publications To add articles Sybase Central Dropping publications To remove articles Sybase CentralTo modify an existing publication SQL To delete a publication Sybase Central To delete a publication SQLSee also the Drop Publication statement ASA SQL Reference, Design issues overview Publication design for Adaptive Server Anywhere Conditions for valid articles Design tips for performance Pay attention to Update Publication Triggers In particular Here is a simple database that illustrates the problem Contact exampleThree tables are described in more detail as follows Following information Those customers assigned to them, from the Customer table106 Partitioning the Customer table in the Contact example Partitioning the Contact table in the Contact exampleTerritory realignment in the Contact example Along with the Customer RepsProperly transferred to the new sales representative For which there is no longer a Customer Special Update statement for publications ∙ SalesRep table Understanding this helps in designing efﬁcient publicationsAssume the following data ∙ Customer table SalesRepData Publication Name rep1 Before list Sharing rows among several subscriptions Policy exampleMany-to-many relationship in the database Involving the sales rep subscribed to the data With the following informationEntire SalesRep table 113 Publication Territory realignment with a many-to-many relationship Contact example on Remote databases contain the proper data 116 Can be multi-valued Customer being transferred Where custkey = OldRow.custkeyThat this subquery can be multi-valued Dealing with the customer, taken from the Policy table Customer SQL Remote Design for Adaptive Server Anywhere Managing conﬂicts ID Rep Dept Ann Marc How SQL Remote handles conﬂicts Must be excluded from the installation by proper designSQL Remote installation at the consolidated database Updating Implementing conﬂict resolution Using conﬂict resolution triggers Create Trigger trigger-name Referencing OLD AS oldval Conﬂict resolution examples Resolving date conﬂicts Resolving inventory conﬂicts Increments from the two updates. For example Reporting conﬂicts Designing to avoid referential integrity errors Designing triggers to avoid errorsIncludes the salesorder table Page Using global autoincrement default column values Ensuring unique primary keys Declaring default global autoincrement Setting the Globaldatabaseid value Primary key values for Global Default Autoincrement values To set the global database identiﬁcation numberDatabase will have Globaldatabaseid set to How default values are chosen Using primary key pools Primary key pool table Replicating the primary key poolTo replicate the primary key pool SQL Filling and replenishing the key pool 136 Cursor for Adding new customers Else Primary key pool summary Insert Creating subscriptions To create and manage subscriptions in Sybase Central For more information, see Create Subscription statement on 140 SQL Remote Design for Adaptive Server Enterprise 141 Design overview Creating publications Creating whole-table articlesCreating articles containing some of the columns in a table Creating articles containing some of the rows in a table Creating an article using a Where clause To create an article using a Where clauseCreating an article using a subscription column To create an article using a subscription column Spaddremotetable tablenameSpaddarticle publicationname, tablename NULL, columnname Publication design for Adaptive Server Enterprise Insert Succeeds Two tables described earlier in this chapter To handle this case, using an exampleContain the subscription column 149 150 Are realigned Adding a subscription-list column to the Contact table Exec spcreatepublication ’SalesRepData’ go Log entries are values, not subscribers Maintaining the subscription-list column Update on the Contact tableUpdate on the Customer table For the following operations Tuning extraction performance SQL Remote Design for Adaptive Server Enterprise To create a subscription view Create a view that contains this subquery. For example156 Solving the problem 158 Foreign KEY Subscriptions to this publication take the following form These objects159 Triggers 161 For Insert AS Begin Tuning extraction performance for shared rows Ensure the quotedidentiﬁer option is set to on 163 Customer Managing conﬂicts Database objects to handle the resolution Consolidated database, no row will be updatedAny conﬂict resolution procedures are called When the conﬂicting message arrived Table only ever contains a single row Names of the conﬂict resolution objectsRemoterowtable. These three are discussed in turn This table must have the same column names ﬁrst conﬂict resolution example Two-table database is as follows168 Follows Conﬂict-causing UpdateAfter the procedure is run, the rows in the OldCustomer @lostname value is the value that was overridden by Second conﬂict resolution example To test the exampleConﬂictLog table has a single row, showing the conﬂict User ID of the remote user. The table is as follows It when the procedure is executedLost and won names Replaces it with the value that was previously present User ID of the remote user is stored by the Message Agent Where conﬂict resolution is carried out by Before triggersThere are several points of note here Currentremoteuser column of the temporary table #remote 173 Page Primary key pool Columns of this table have the following meanings 175 To replicate the primary key pool 176 177 Adding new customers Testing the key pool To test the primary key pool179 Primary key pool summary Spsubscription create, puborders SamS ’856’ Page SQL Remote Page SQL Remote replication installation Deploying and Synchronizing Databases185 Deployment overview Changes to avoid on a running system Resolve update conﬂicts are all easy to doTest before deployment Conﬂicts as they occurPage Synchronizing databases Mixed operating systems and database extraction Example Creating a database from the reload ﬁles Using the extraction utilityWhere path is the path of the reload command ﬁle 191 To create a remote database from the reload ﬁle Using the extraction utility from Sybase Central Before extracting a database Designing an efﬁcient extraction procedure To extract a database for a remote user Sybase Central An efﬁcient approach to extracting many databases Limits to using the extraction utility Extracting groups Using the extraction utility for Adaptive Server Enterprise This setup is illustrated in the following diagram Customizing the system tables Synchronizing data over a message system SQL Remote Administration 199 Management overview Managing SQL Remote permissions Granting and revoking Publish permissions To revoke Publish permissions Sybase Central To create a new user as the publisher Sybase CentralTo make an existing user the publisher Sybase Central 202 Exec sppublisher ’SBeaulieu’ go Granting and revoking Remote and Consolidate permissions Granting Remote permissions Use an Smtp e-mail system To make an existing user remote Sybase CentralFollowing options Send messages to e-mail address sbeaulieu@acme.com Selecting a send frequency Statement is executed automatically at the remote database Permissions to user hquser, using the ﬁle message linkGranting Consolidate permissions Agent is run Assigning permissions in multi-tier installations To revoke Remote permissions Sybase CentralPermission from user SBeaulieu Publish Using message types Working with message types Using Sybase Central to work with message types To add a message type Sybase CentralTo alter a message type Sybase Central To create a message type SQL Using commands to work with message typesTo drop a message type Sybase Central Create Remote Message Type type-nameADDRESS address-string Create Remote Message Type statement on To alter a message type SQLTo drop a message type SQL 213 Setting message type control parameters To set a message control parameter Adaptive Server Anywhere By using the ﬁle message system ﬁle message system215 Ftp message system Troubleshooting ftp problems Smtp message system Mote messages218 SQL Remote Administration Mapi message system Sharing SMTP/POP addressesSupported operating systems on VIM message system VIM message control parameters Names are ssremote and dbremote, respectively Running the Message AgentMessage Agent batch and continuous modes Enterprise works on To run the Message Agent in batch mode Replication system recovery proceduresTo run the Message Agent in continuous mode Connections used by the Message Agent Adaptive Server Enterprise transaction log and backup Ensuring consistent Message Agent settingsSee the sections Transaction log and backup management on Management on Troubleshooting errors at remote sites Message Agent and replication security Use either the -roor the -rtMessage Agent option Execute the following command against the remote databaseTo conﬁgure a consolidated site to receive log information For more information, see The Message Agent on Tuning Message Agent performance Tuning throughput by controlling Message Agent threading Tuning throughput by caching messages Tuning incoming message polling Polling interval Requesting resends Example231 Tuning the message sending process When a remote user requests that a message be To those when tuning the incoming-message polling frequencyYour choices dictate how often updates are sent to Resending messages Dbremote -ru 1h Encoding and compressing messages Encoding scheme Creating custom encoding schemes Message tracking system Status information in the remoteuser tableTracking messages by transaction log offsets Cannot be a later offset than logsent Agent -loption to change this settingAre offsets in the local database transaction log, Transaction log Handling of lost or corrupt messages Its resendcountPage Administering SQL Remote for Adaptive Server Anywhere 241 Running the Message Agent as a service Starting the Message Agent Suggested practice is to grant Remote DBA authority at Full DBA permissions from the Message Agent When connectingFull DBA permissions on the database DBA authority grants them no extra permissionsPage Ignoring errors Error reporting and handlingDefault error handling Agent output Following stored procedure implements this notiﬁcation Implementing error handling proceduresExample e-mailing notiﬁcation of errors 246 Columns have the following meaning 247 Commit Work Here is a sample insert into the table from the above error 248 Transaction log and backup management Setting the transaction log directory Backup utility options Using the live directory as the transaction log directorySuch a directory is kept in proper shape Following command line Using the backup directory as the transaction log directory 252 Managing old transaction logs Recovery with a single transaction log To recover the database254 Start the database using the following command line To recover from media failure on the C driveBackup the mirrored transaction log d\mirdir\consol.mlg Recovery with multiple transaction logs Backup the mirrored transaction log d\mirdir\cons.mlg Backups daily using the following commandCommand line would be Make a copy of the database and log ﬁle Backup procedures at remote databases Apply the renamed transaction logs in order, as followsRestart your system as normal Upgrading consolidated databases 258 To unload and reload a consolidated database manual Using passthrough mode Uses and limitations of passthrough mode Procedure on the replicate side has the correct effect Operations not replicated in passthrough modeOn a running SQL Remote setup However, the following dynamic SQL statement is replicated Administering SQL Remote for Adaptive Server Enterprise 263 How the Message Agent for Adaptive Server Enterprise works Scanning the transaction logMessage Agent on Administering SQL Remote for Adaptive Server Enterprise Stable queue Message Agent operation phases 266 TransactionStable Logqueue Message Agent 267 268 For setup instructions, see Setting Up SQL Remote on Running multiple Message Agents To execute Agent output Protecting against media failure on the transaction log Stable queue recovery issues Transaction log management Freed by Dump Transaction With the following commandTruncation point can be reset with the following command 274 Making schema changes Schema modiﬁcations Using SQL Remote with Replication Server 277 When you need to use the SQL Remote Open Server Architecture for Replication Server/SQL Remote installations How the pieces ﬁt together Message system Stable Queue Agent SQL Remote Open Server is the following executable Information to retrieve it when it startsRemote Open Server on On Windows operating systems, the SQL Remote Open Server is Setting up SQL Remote Open Server Same regardless of previous installationsAdd the SQL Remote Open Server to the setup This stage is To set up the SQL Remote Open Server Page Set the dsinumthreads parameter Conﬁguring Replication ServerSet the dsixactgroupsize parameter Create replication deﬁnitions for SQL Remote data Suspend and restart the connection Other issues 288 This part presents reference material for SQL Remote Page Utilities and Options Reference 291 Message Agent Tracking system to ensure message deliveryDbremote ssremote options directory Utilities and Options Reference Listing, see Connections used by the Message Agent on Replication security on 295 Languagename,charsetname,sortorder For more information, see Running multiple Message Agents on Page Dbremote -rd 30s Page Windows Registry, at the following locationYou should create a ﬁle named dbremote.ini NetWare Database Extraction utility Extracting a remote database in Sybase Central Extraction utility 303 304 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 Server Values default to the -cvalues Default value for the open server name is SSQueueGain access to the SQL Remote system tables Name of the executable is as followsPage SQL Remote options Page Yy yyyy mm mmm dd 318 Hh nn mm Ss.s Relationships on SQL Remote event-hook procedures Sphookdbremotebegin and sphookssrmtbeginSphookdbremoteend and sphookssrmtend Sphookdbremoteshutdown and sphookssrmtshutdown Sphookdbremotereceivebegin and sphookssrmtreceivebeginSphookdbremotereceiveend and sphookssrmtreceiveend Sphookdbremotemessagesent and sphookssrmtmessagesent Sphookdbremotesendbegin and sphookssrmtsendbeginSphookdbremotesendend and sphookssrmtsendend Sphookdbremotemessagemissing and sphookssrmtmessagemissing Has applied a set of messages from a user 323Page System Objects for Adaptive Server Anywhere 325 SQL Remote system tables Sysarticle tableEach row describes an article in a SQL Remote publication Sysarticlecol table It is in, and the publication it is part327 Sysremoteoptiontype table Syspublication tableSysremoteoption table Each row describes a SQL Remote publication Publisher address Sysremotetype tableSysremoteuser table 329 330 Consolidate Syssubscription table Remote permissions to one publication331 332 Sysarticlecols view SQL Remote system viewsSysarticles view Syspublications view Sysremoteoptions view Sysremoteusers view Syssubscriptions view Each row lists information about a subscription335 336 System Objects for Adaptive Server Enterprise 337 Manage SQL Remote information #remote tableSrarticle table Table has a single row Databases in the same session Srarticlecol tableSrmarker table 339 Srpassthrough table Srobject tableSroption table Each row describes a replication option used by SQL Remote Srpublication table Srpublisher tableSrremoteoption table Srremotetype table Srremoteoptiontype tableSrremotetable table 342 Srremoteuser table 343 344 Received Srsubscription table 345 Srarticles view Srarticlecols viewSrpublications view Srremoteoptions view Srremotetables viewSrremotetypes view Srremoteusers view 348 Srsubscriptions view 349 Stable queue Stable Queue tablesSrqueuestate table 350 Srtransaction table 351 Each row marks the corresponding row in srtransaction Srconﬁrmedtransaction tableSrqueuecoordinate table 352 Command Reference for Adaptive Server Anywhere 353 354 Must have DBA authority Alter Remote Message Type statementBeen created Automatic commit Create Publication statement Create Publication statement ASA SQL Reference,Subscribe by expression Create Remote Message Type statement SQL Remote ASA SQL Create Remote Message Type statementMessages from a database Create Remote Message Type message-system Create Subscription statement Create Subscription statement SQL Remote ASA SQL Reference Create Trigger statement Table and thus requires exclusive use of the table Update statement onMust have Resource authority and have Alter permissions on Create Trigger statement SQL Remote ASA SQL Reference Drop Publication statement Drop Publication statement ASA SQL Reference, Drop Remote Message Type statement SQL Remote ASA SQL Drop Remote Message Type statementGranted Remote or Consolidate permissions with this type Drop Remote Message Type message-system Drop Subscription statement Drop Subscription statement SQL Remote ASA SQL Reference Grant Consolidate statement SQL Remote ASA SQL Reference Grant Consolidate statementCurrent database Send Every AT ’hhmm ss’ Grant Publish statement Grant Remote statement Connected from the Message Agent Identified by passwordGrant Remote DBA statement Grant Remote DBA statement SQL Remote ASA SQL Reference Passthrough statement Passthrough modeSppassthrough procedure on Passthrough statement SQL Remote ASA SQL Reference, Subscriptions for a remote user in a single transaction Remote Reset statementRemote Reset statement SQL Remote ASA SQL Reference, No automatic commit is done by this statement SQL Remote messages from this database Sprevokeconsolidate procedure onRevoke Consolidate statement Automatic commit. Drops all subscriptions for the user Revoke Publish statement SQL Remote ASA SQL Reference Revoke Publish statementCurrent publisher Revoke Publish from userid Messages from this database Sprevokeremote procedure onRevoke Remote statement Revoke Remote statement SQL Remote ASA SQL Reference Revoke Remote DBA statement Revoke Remote DBA statement SQL Remote ASA SQL Reference Splinkoption procedure on SET Remote Option statementMessage link Start Subscription statement Start Subscription Stop Subscription statement Stop Subscription Synchronize Subscription statement Synchronize Subscription Update statement Update statement SQL Remote ASA SQL Reference,Create Trigger statement on Command Reference for Adaptive Server Enterprise 379 380 Spaddarticle procedure Making schema changes on SalesRepData382 Spaddarticlecol procedure To add a column to an article in a publicationSpaddarticlecol publicationname Spaddremotetable procedure To mark a table for SQL Remote replication RemoteCustomer, respectively Default conﬂict resolutionRemote rows are stored in tables named oldCustomer 385 To create a publication Spcreatepublication procedureSpdroppublication procedure on Spcreatepublication publicationname To drop a publication from the database Spdroppublication procedureSpcreatepublication procedure on Spdroppublication publicationname Spdropremotetype procedure Spdropremotetype typename Spdropsqlremote procedure Spqueuedrop procedure onProcedure on Spgrantconsolidate procedure Databases acting as remote databases See also Description Example 392 Spgrantremote procedure One of the publications in the current database Current database must be granted Remote permissions usingSingle quotes Speciﬁed 395 Splinkoption procedure SET Remote Option statement onDatabases Mapi message system on ﬁle message system onFtp message system on Smtp message system on Spmodifyarticle procedure To change the description of an article in a procedure Subscription expression Expression that is the repkey column399 Spremoveremotetable procedure on Spmodifyremotetable procedureSpaddremotetable procedure on Managing conﬂicts on 401 Sppassthrough procedure Sppassthroughpiece procedure To build a long SQL statement for passthroughSppassthroughpiece string 404 Sppassthroughstop procedure resents the list of recipients Sppassthroughstop procedureResents passthrough mode Currently being built Sppassthroughsubscription procedure StatementsSppassthroughsubscription publicationname Sppassthroughuser procedure Sppassthroughuser username Called directly Sppopulatesqlanywhere procedureConsolidated database Sppopulatesqlanywhere Sppublisher procedure Sppublisher username Be called directly Spqueueclean procedureSpqueueclean Log was scanned Spqueueconﬁrmeddeleteold procedure Spqueueconﬁrmeddeleteold Spqueueconﬁrmedtransaction procedure Match this offsetSpqueueconﬁrmedtransaction offset Spqueuedeleteold procedure Been conﬁrmed by all remote databasesSpqueuedeleteold Spqueuedrop procedure Spdropsqlremote procedure on Spqueuedumpdatabase procedure Spqueuedumptransaction procedure onStable queue recovery issues on Spqueuedumptransaction procedure Spqueuedumpdatabase procedure onSpqueuedumptransaction Spqueuegetstate procedure QueueSpqueuegetstate Spqueuelogtransferreset procedure Be called directly. It resets the page and row IDs to zeroSpqueuelogtransferreset Spqueueread procedure Use by the Message AgentSpqueueread startoffset Spqueuereset procedure Ready for a new SQL Remote setupSpqueuereset Spqueuesetconﬁrm procedure Users in the srqueuestate tableSpqueuesetconﬁrm conﬁrmoffset Spqueuesetprogress procedure Spqueuesetprogress pageid Spqueuetransaction procedure Spqueuetransaction offset Spremote procedure Message tracking information in the srremoteuser tableSpremote operation Spremoteoption procedure To set a SQL Remote option 426 Spremotetype procedure Spdropremotetype procedure onAlter Remote Message Type statement on To remove an article from a publication Spremovearticle procedureSpaddarticle procedure on Spremovearticle publicationname Spremovearticlecol procedure To remove a column from an article in a publicationSpremovearticlecol publicationname To mark a table as unavailable for SQL Remote replication Spremoveremotetable procedureSpmodifyremotetable procedure on Spremoveremotetable tablename Sprevokeconsolidate procedure Spgrantconsolidate procedure onSprevokeconsolidate username Sprevokeremote procedure Sprevokeremote username Spsubscription procedure Spsubscriptionreset Spsubscriptionreset procedureTo reset all SQL Remote information for all remote users Srsubscription tables to zero or Null Appendices 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 445 Supported message systems Supported operating systems Windows NT/2000/XP All message links 448 Symbols Index Index 450 451 Current Remote User 452 Sqlremote 453 454 LTM 455 456 Subscribebyremote 457 Remote 458 459 460 Send Every 461 462 463 Tempdb 464 465 466 467 Unix