Specifies additional objects to include in or specifically exclude from the publication. These objects are created on the subscriber’s database replica.
In addition to the tables included in the publication, there can be other database objects that are required for the team solution to work on the subscriber’s replica, such as views, stored procedures, and triggers.
You can exclude objects by clearing the check mark next to the object. For example, when you include main tables in the publication, all associated details and lookup tables are included. If there is a lookup table you do not want available offline for security reasons, you can exclude that table.
When adding or excluding tables from the publication, it is recommended you test your solution offline to verify that all required objects are included in the publication.
Filter list below to show
Select the objects you want to include in the list.
Database objects list
Displays the database objects by object name and type based on the filter you specify. Select to include a database object, and clear to remove it from the publication.
Re-create SQL Publication
Whenever you make changes to your team solution that will impact your offline publication, you must re-create the publication to make those changes available to your users. If you make changes to the schema without re-creating your publications, your offline users may not be able to synchronize their changes.
For information about | See |
Identifying objects to include in your publication | Specifying Specific Objects for Offline Use |
Specifying permissions for your publication | Defining Permissions for Offline Publications |
Making your team solution available offline | Allowing Users to Work Offline |
Changing the details of the offline publication | Modifying an Offline Publication |
Requirements and guidelines for creating offline publications | Planning Offline Capabilities |
Making your team solution available offline | Installing Offline Support for the Solution |
Defining a table hierarchy for your solution database | Setting up a Table Hierarchy |