Hi,
I'm trying to get database mirror working with SQL 2005... but I'm not having much luck. Any pointers would be appreciated.
I've got 3 separate machines in a work group configuration. There isn't a primary dns suffix so I'm just using the simple machine names.
I've configured the certificates, logins/users, and end points.
On the mirror I do the ALTER DATABASE SET PARTNER and that works.
On the primary I do the ALTER DATABASE SET PARTNER and it fails with the error:
The Service Broker ID of the remote copy of database 'X' does not match the ID on the principal server (msg 1436).
I've followed the trouble shoot steps from BOL but no joy.
Any suggestions
Regards,
Rob
SQL 2005 Mirroring... Remote Broker ID does not match the ID on the principal
Hot Topic
- How to add/(connect to) database in SQL Server 2005 Express?
- the most stupid sum question
- Dynamic SQL Server Destination???
- Running parallel causes some issues
- Problems with SQL 2005 Export Wizard
- Time Intelligence gives this failure if X64bit installed on a different drive
- how do i backup my users + passwords?
- BreakpointManager,BreakpointSite
- List both SQL2000&2005 instance using SQLDMO
- How to stop a package
SQL Server
- ActiveX Script transformation column in SSIS but how???
- Under Linux, can I connect to SQL Server which is authenticated by windows only?
- Discard Rows in a flat file
- Join tables Count problems
- SQL Server 2005 Enterprise Evaluation Edition - 'corrupted' downloaded SETUP.exe
- SSIS will not start after SQL Server 2005 SP1 upgrade
- The never ending DTSX package
- SQL Server error '80040e14' (The server encountered a stack overflow during compile time. )
- Import Wizard using a PosgreSQL Source
- How to add the total balances of previous year into the next year?
SQL 2005 Mirroring... Remote Broker ID does not match the ID on the principal
enrikeperez
So, there are only two ways to get this error message.
1. this isn't the same database. i.e. you restored a different database
2. you altered the database, giving it a new broker ID. i.e. ALTER DATABASE foo SET NEW_BROKER. so, try the backup/restore again.
Lemme know if that works.
thanks,
mwistrom@youknowMICROSOFTthecompany.com
Wainz
Success!
After restoring the DB on the mirror I also needed to backup the transaction log on the primary and then restore the log on the mirror.
Thanks!
Rob
Alexei_shk
Thanks for responding... it was a help.
The problem turned out to be how I restored the databases.
I started out with a sql2000 backup of my database, which I restored to the primary and then to the mirror.
I've changed this to now be a two stepper: restore the sql2000 to the primary, do a backup of the primary, restore that backup on the mirror.
I no longer get the broker error... but now get an error complaining about the secondary database not being rolled forward. Any thoughts on that one (I'm thinking the problem is with the backup I did on the primary).
Thanks!
Rob MacFadyen