Hi,
I'm planning to move MS SQL Server 2000 instance to another server. I know
that the easiest way is to copy data directory from one machine to another
and set new server name to the old one. Because of some reasons I can't do
it in thisy way. Besides that I don't watn to move all databases but some of
them. Unfortunately, some of these databases are replicated (part of them is
published and another part is subscibed).
How to move MSSQL instance to another machine keeping replication working
properly without starting replication from scratch? Is there way to restore
database (published or subscribed) with already set replication?
Thanks
Marcin> Hi,
> I'm planning to move MS SQL Server 2000 instance to another server. I know
> that the easiest way is to copy data directory from one machine to another
> and set new server name to the old one. Because of some reasons I can't do
> it in thisy way. Besides that I don't watn to move all databases but some
of
> them. Unfortunately, some of these databases are replicated (part of them
is
> published and another part is subscibed).
> How to move MSSQL instance to another machine keeping replication working
> properly without starting replication from scratch? Is there way to
restore
> database (published or subscribed) with already set replication?
> Thanks
> Marcin
--
You can't do it. According to SQL Server Books Online:
Restoring Backups of Replicated Databases to a Different Server or Database
When you restore a backup of a replicated database to a server or database
other than the one on which it was created, your replication settings
cannot be preserved. For publishing databases and merge subscribing
databases, a full restore of the database and logs is followed by an
automatic removal of replication meta data from the database when the
database or server you restore to differs from the one on which the backup
was created.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Showing posts with label directory. Show all posts
Showing posts with label directory. Show all posts
Monday, March 12, 2012
replication and data move
Hi,
I'm planning to move MS SQL Server 2000 instance to another server. I know
that the easiest way is to copy data directory from one machine to another
and set new server name to the old one. Because of some reasons I can't do
it in thisy way. Besides that I don't watn to move all databases but some of
them. Unfortunately, some of these databases are replicated (part of them is
published and another part is subscibed).
How to move MSSQL instance to another machine keeping replication working
properly without starting replication from scratch? Is there way to restore
database (published or subscribed) with already set replication?
Thanks
Marcin
> Hi,
> I'm planning to move MS SQL Server 2000 instance to another server. I know
> that the easiest way is to copy data directory from one machine to another
> and set new server name to the old one. Because of some reasons I can't do
> it in thisy way. Besides that I don't watn to move all databases but some
of
> them. Unfortunately, some of these databases are replicated (part of them
is
> published and another part is subscibed).
> How to move MSSQL instance to another machine keeping replication working
> properly without starting replication from scratch? Is there way to
restore
> database (published or subscribed) with already set replication?
> Thanks
> Marcin
You can't do it. According to SQL Server Books Online:
Restoring Backups of Replicated Databases to a Different Server or Database
When you restore a backup of a replicated database to a server or database
other than the one on which it was created, your replication settings
cannot be preserved. For publishing databases and merge subscribing
databases, a full restore of the database and logs is followed by an
automatic removal of replication meta data from the database when the
database or server you restore to differs from the one on which the backup
was created.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
I'm planning to move MS SQL Server 2000 instance to another server. I know
that the easiest way is to copy data directory from one machine to another
and set new server name to the old one. Because of some reasons I can't do
it in thisy way. Besides that I don't watn to move all databases but some of
them. Unfortunately, some of these databases are replicated (part of them is
published and another part is subscibed).
How to move MSSQL instance to another machine keeping replication working
properly without starting replication from scratch? Is there way to restore
database (published or subscribed) with already set replication?
Thanks
Marcin
> Hi,
> I'm planning to move MS SQL Server 2000 instance to another server. I know
> that the easiest way is to copy data directory from one machine to another
> and set new server name to the old one. Because of some reasons I can't do
> it in thisy way. Besides that I don't watn to move all databases but some
of
> them. Unfortunately, some of these databases are replicated (part of them
is
> published and another part is subscibed).
> How to move MSSQL instance to another machine keeping replication working
> properly without starting replication from scratch? Is there way to
restore
> database (published or subscribed) with already set replication?
> Thanks
> Marcin
You can't do it. According to SQL Server Books Online:
Restoring Backups of Replicated Databases to a Different Server or Database
When you restore a backup of a replicated database to a server or database
other than the one on which it was created, your replication settings
cannot be preserved. For publishing databases and merge subscribing
databases, a full restore of the database and logs is followed by an
automatic removal of replication meta data from the database when the
database or server you restore to differs from the one on which the backup
was created.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
replication and data move
Hi,
I'm planning to move MS SQL Server 2000 instance to another server. I know
that the easiest way is to copy data directory from one machine to another
and set new server name to the old one. Because of some reasons I can't do
it in thisy way. Besides that I don't watn to move all databases but some of
them. Unfortunately, some of these databases are replicated (part of them is
published and another part is subscibed).
How to move MSSQL instance to another machine keeping replication working
properly without starting replication from scratch? Is there way to restore
database (published or subscribed) with already set replication?
Thanks
Marcin> Hi,
> I'm planning to move MS SQL Server 2000 instance to another server. I know
> that the easiest way is to copy data directory from one machine to another
> and set new server name to the old one. Because of some reasons I can't do
> it in thisy way. Besides that I don't watn to move all databases but some
of
> them. Unfortunately, some of these databases are replicated (part of them
is
> published and another part is subscibed).
> How to move MSSQL instance to another machine keeping replication working
> properly without starting replication from scratch? Is there way to
restore
> database (published or subscribed) with already set replication?
> Thanks
> Marcin
--
You can't do it. According to SQL Server Books Online:
Restoring Backups of Replicated Databases to a Different Server or Database
When you restore a backup of a replicated database to a server or database
other than the one on which it was created, your replication settings
cannot be preserved. For publishing databases and merge subscribing
databases, a full restore of the database and logs is followed by an
automatic removal of replication meta data from the database when the
database or server you restore to differs from the one on which the backup
was created.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
I'm planning to move MS SQL Server 2000 instance to another server. I know
that the easiest way is to copy data directory from one machine to another
and set new server name to the old one. Because of some reasons I can't do
it in thisy way. Besides that I don't watn to move all databases but some of
them. Unfortunately, some of these databases are replicated (part of them is
published and another part is subscibed).
How to move MSSQL instance to another machine keeping replication working
properly without starting replication from scratch? Is there way to restore
database (published or subscribed) with already set replication?
Thanks
Marcin> Hi,
> I'm planning to move MS SQL Server 2000 instance to another server. I know
> that the easiest way is to copy data directory from one machine to another
> and set new server name to the old one. Because of some reasons I can't do
> it in thisy way. Besides that I don't watn to move all databases but some
of
> them. Unfortunately, some of these databases are replicated (part of them
is
> published and another part is subscibed).
> How to move MSSQL instance to another machine keeping replication working
> properly without starting replication from scratch? Is there way to
restore
> database (published or subscribed) with already set replication?
> Thanks
> Marcin
--
You can't do it. According to SQL Server Books Online:
Restoring Backups of Replicated Databases to a Different Server or Database
When you restore a backup of a replicated database to a server or database
other than the one on which it was created, your replication settings
cannot be preserved. For publishing databases and merge subscribing
databases, a full restore of the database and logs is followed by an
automatic removal of replication meta data from the database when the
database or server you restore to differs from the one on which the backup
was created.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Saturday, February 25, 2012
replicating with Active directory
Is they any feature that allows replication between Active Directory an SQL
server. I know I can write an assembly to do it but I'm checking on easier
ways first.
--
Regards,
Gary BlakelyHi
You can not replicate Active Directory to SQL Server, but you can interogate
the active directory using the ADSI adapter see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adsi/adsi/active_directory_service_interfaces_adsi.asp
and
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adsi/adsi/joining_heterogeneous_data.asp
If you want to have more resilience with your AD then you can replicated to
another Active Directory servers see
http://msdn2.microsoft.com/en-us/library/ms677921.aspx
John
"GaryDean" wrote:
> Is they any feature that allows replication between Active Directory an SQL
> server. I know I can write an assembly to do it but I'm checking on easier
> ways first.
>
> --
> Regards,
> Gary Blakely
>
>|||Hi Gary,
Did you mean that you want to setup a replication between two different
domains?
If you have to set up replication across two non-trusted domains or
workgroups by using Windows authentication, you must configure pass-through
authentication. Configure a local Windows account on both the Publisher and
the Subscriber that has the same name and password. After you configure
this account, use the account to start the SQL Server Agent service on the
Publisher for push subscriptions and on the Subscriber for pull
subscriptions. Make sure that this account is configured according to the
"Setting up Windows Services Accounts" topic in SQL Server Books Online.
If the user tries to make a network connection to a remote computer that is
in a non-trusted domain, the logon proceeds as if the user is connecting to
an account on the remote computer. The remote computer authenticates the
logon credentials against its directory database. If the account is not
defined in the directory database, but the guest account on the remote
computer is enabled and the guest account has no password set, the user
logs on with guest permissions. If the guest account is not enabled, the
logon is not successful.
For more information, please refer to:
HOW TO: Replicate Between Computers Running SQL Server in Non-Trusted
Domains or Across the Internet
http://support.microsoft.com/kb/321822/en-us
Please feel free to let me know if you have any other questions or
concerns.
Sincerely yours,
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Hi,
Happy New Year!
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
server. I know I can write an assembly to do it but I'm checking on easier
ways first.
--
Regards,
Gary BlakelyHi
You can not replicate Active Directory to SQL Server, but you can interogate
the active directory using the ADSI adapter see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adsi/adsi/active_directory_service_interfaces_adsi.asp
and
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adsi/adsi/joining_heterogeneous_data.asp
If you want to have more resilience with your AD then you can replicated to
another Active Directory servers see
http://msdn2.microsoft.com/en-us/library/ms677921.aspx
John
"GaryDean" wrote:
> Is they any feature that allows replication between Active Directory an SQL
> server. I know I can write an assembly to do it but I'm checking on easier
> ways first.
>
> --
> Regards,
> Gary Blakely
>
>|||Hi Gary,
Did you mean that you want to setup a replication between two different
domains?
If you have to set up replication across two non-trusted domains or
workgroups by using Windows authentication, you must configure pass-through
authentication. Configure a local Windows account on both the Publisher and
the Subscriber that has the same name and password. After you configure
this account, use the account to start the SQL Server Agent service on the
Publisher for push subscriptions and on the Subscriber for pull
subscriptions. Make sure that this account is configured according to the
"Setting up Windows Services Accounts" topic in SQL Server Books Online.
If the user tries to make a network connection to a remote computer that is
in a non-trusted domain, the logon proceeds as if the user is connecting to
an account on the remote computer. The remote computer authenticates the
logon credentials against its directory database. If the account is not
defined in the directory database, but the guest account on the remote
computer is enabled and the guest account has no password set, the user
logs on with guest permissions. If the guest account is not enabled, the
logon is not successful.
For more information, please refer to:
HOW TO: Replicate Between Computers Running SQL Server in Non-Trusted
Domains or Across the Internet
http://support.microsoft.com/kb/321822/en-us
Please feel free to let me know if you have any other questions or
concerns.
Sincerely yours,
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Hi,
Happy New Year!
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
Monday, February 20, 2012
Replicating Matched MS SQL HR Data to Active Directory's Metadirectory fields
I've managed to do the add linkedserver stuff and pull up of some active
directory information.
I even matched up some data but could never insert anything into the AD Meta
fields.
I used this article,
http://msluder.dk/Resources/ADSI%20S...%20HTML/dq.htm ,which never
promised insert capabilities.
But if this is all it can do is give the ability to run some obscure reports
then it's hardly useful.
What I would like to do is create a view that would dynamiclly update the AD
Meta data from the Human Resources Database using the CN and / or
Primary-Email Address as the linking field.
That way when people change office numbers or as new employees start that
Meta information would be updated once it was entered or altered by HR.
It seems this would be possible via some kind of replication or event based
update through the SQL Server.
Any one have some ideas on this?
-Ethan
Ethan,
have a look at the Microsoft Script Repository
(http://www.microsoft.com/downloads/d...n&FamilyID=B4C
B2678-DAFB-4E30-B2DA-B8814FE2DA5A) there are scripts there to update AD.
HTH,
Paul Ibison
|||Have a look at the Replication Distributor Interface Reference in BOL.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
directory information.
I even matched up some data but could never insert anything into the AD Meta
fields.
I used this article,
http://msluder.dk/Resources/ADSI%20S...%20HTML/dq.htm ,which never
promised insert capabilities.
But if this is all it can do is give the ability to run some obscure reports
then it's hardly useful.
What I would like to do is create a view that would dynamiclly update the AD
Meta data from the Human Resources Database using the CN and / or
Primary-Email Address as the linking field.
That way when people change office numbers or as new employees start that
Meta information would be updated once it was entered or altered by HR.
It seems this would be possible via some kind of replication or event based
update through the SQL Server.
Any one have some ideas on this?
-Ethan
Ethan,
have a look at the Microsoft Script Repository
(http://www.microsoft.com/downloads/d...n&FamilyID=B4C
B2678-DAFB-4E30-B2DA-B8814FE2DA5A) there are scripts there to update AD.
HTH,
Paul Ibison
|||Have a look at the Replication Distributor Interface Reference in BOL.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Labels:
active,
activedirectory,
database,
directory,
fields,
insert,
ive,
linkedserver,
managed,
matched,
metadirectory,
microsoft,
mysql,
oracle,
pull,
replicating,
server,
sql,
stuff
Subscribe to:
Posts (Atom)