However, depending on the replication scenario, you may not need to restore the
distribution database. Often replication is best ???restored??? by dropping subscriptions
and publications and re-creating them. This was usually the case in SQL 2000, and
could remain a preferable way of rebuilding replication rather than restoring the distribution
database.
The one large exception to that would be in an elaborate replication topology. If
you??™re replicating between a handful of servers, simply rebuilding the replication publications
should suffice. If the topologies have thousands of subscribers, publishing subscribers,
and large databases, restoring the distribution database will save hundreds of
man hours.
CHAPTER 3 n RESTORING A DATABASE 68
Resource
You may have noticed that the size of the master database is considerably smaller in SQL
Server 2005/2008 compared to SQL Server 2000 and earlier. That??™s because the code used
to generate pseudotables and system views is now located in a hidden system database
called resource. This database does not appear in SQL Server Management Studio, as you
can see in Figure 3-10.
Pages:
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164