Thursday, March 22, 2012

Database Mirroring

Hi
In SQL Server 2005 there is a function for Database Mirroring which will
syncronize between 2 sql server databases .
the more details are explained in the following link.
http://www.databasejournal.com/feat...cle.php/3440511
the same option can be done thru SQL Server 2k using replication immediate
update synchronization.
am i right '
RenjithHi
Similar, but different technologies. DB Mirroring does not work at data
level, it works at page level. It is more like log shipping than replication
.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Renjith" wrote:

> Hi
> In SQL Server 2005 there is a function for Database Mirroring which will
> syncronize between 2 sql server databases .
> the more details are explained in the following link.
> http://www.databasejournal.com/feat...cle.php/3440511
> the same option can be done thru SQL Server 2k using replication immediate
> update synchronization.
> am i right '
> Renjith
>|||"Renjith" schrieb:

> Hi
> In SQL Server 2005 there is a function for Database Mirroring which will
> syncronize between 2 sql server databases .
> the more details are explained in the following link.
> http://www.databasejournal.com/feat...cle.php/3440511
> the same option can be done thru SQL Server 2k using replication immediate
> update synchronization.
> am i right '
> Renjith
>
No. The replication will not transport new datatypes, defaults or rules.
Every change to the schema (adding/dropping tables or columns), new indexes
or constraints etc. require a new snapshot and a reinitialization of the
subscribers. And this means manual work!
Furthermore, all the user accounts and their permissions are completely
outside of the replication.
Next: to provide database mirroring, you need short intervals for
replication. This can only be achieved with transactional replication. And
transactional replication doesn't replicate any timestamp fields or identity
columns - they would be lost in the database duplicate.
The only way to provide database mirroring on SQL Server 2000 is (as far as
I know) the tool SDynRep from the DoMO ITC GmbH. It adds all the above
mentioned things to the replication and automatises the whole thing. Very
proprietary and not cheap!
The SQL Server 2005 database mirroring really fills a gap.
Logshipping comes close to this, but has a negative impact on your regular
backup strategy!|||more similar to current "Log Shipping"
Greg Jackson
PDX, Oregon|||Does this require the mirror database to be read-only?
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:BD57381E-2E53-446B-9B08-626AB0A4A35F@.microsoft.com...
> Hi
> Similar, but different technologies. DB Mirroring does not work at data
> level, it works at page level. It is more like log shipping than
replication.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Renjith" wrote:
>
immediate

No comments:

Post a Comment