It??™s actually more accurate to say that a database mirroring session is a Service Broker
application??”just a very specialized version of one. An awful lot of creation and configuration
goes on behind the scenes. Technically, after creating endpoints that are marked
FOR DATABASE_MIRRORING, you only need to set the partner level??”that is, what role the
database plays in mirroring.
CREATE ENDPOINT Endpoint_Mirroring
STATE=STARTED
AS TCP (LISTENER_PORT=7022)
FOR DATABASE_MIRRORING (ROLE=WITNESS)
GO
ALTER DATABASE MirrorTest
SET PARTNER = 'TCP://SPYGLASSTAB:7023'
ALTER DATABASE AdventureWorks
SET WITNESS = 'TCP://SPYGLASSTAB:7042'
Once you??™ve activated all endpoints FOR DATABASE_MIRRORING and you??™ve set the databases
with partner or witness roles, the Service Broker part of things is set.
A Service Broker application is extremely complex to configure simply by virtue of
the number of steps involved. Luckily for us, the steps to configure Service Broker are
performed automatically when you configure database mirroring. With the release-tomanufacturing
(RTM) version of SQL Server 2005 and all of the betas and CTPs, you had
to manually configure the Service Broker aspect for a database mirroring session.
Pages:
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391