Showing posts with label dear. Show all posts
Showing posts with label dear. Show all posts

Monday, March 19, 2012

Maintainence of Replication

Hi Dear...

I have some questions regarding replication in SQL Server 2005.

1. Is it neccessary to have same schema on each side i.e on subsicriber and on publisher?

2. Do replication helps me to replicate the changed schema (of published articals) to the subscribers?

3. If a UDT is defined on publisher and one of its dependent is selected for publication do i need to define the UDT on subscriber manually or it will automatically done for me?

4. pls anyone who can give me the detail known issues and their alternative solutions in regard of maintainence of Replication.

Regards

Mubashar Ahmad

1. Subscriber can have a either the full table, a portion of the table or not at all. You cannot replicate to a totally different schema though.

2. Yes it will replicate ALTER statements.

3. I think you have to do that manaully. However you can set a script to run before the snapshot to create it for you automatically.

4. I dont think anyone can give you that.

Martin

|||

For #3 you have options, see @.schema_option for sp_addarticle.

|||thanks both of you... i ll keep this in mind when i come back to replication.. at the moment i am on long vacations... SmileSmile

Maintainence of Replication

Hi Dear...

I have some questions regarding replication in SQL Server 2005.

1. Is it neccessary to have same schema on each side i.e on subsicriber and on publisher?

2. Do replication helps me to replicate the changed schema (of published articals) to the subscribers?

3. If a UDT is defined on publisher and one of its dependent is selected for publication do i need to define the UDT on subscriber manually or it will automatically done for me?

4. pls anyone who can give me the detail known issues and their alternative solutions in regard of maintainence of Replication.

Regards

Mubashar Ahmad

1. Subscriber can have a either the full table, a portion of the table or not at all. You cannot replicate to a totally different schema though.

2. Yes it will replicate ALTER statements.

3. I think you have to do that manaully. However you can set a script to run before the snapshot to create it for you automatically.

4. I dont think anyone can give you that.

Martin

|||

For #3 you have options, see @.schema_option for sp_addarticle.

|||thanks both of you... i ll keep this in mind when i come back to replication.. at the moment i am on long vacations... SmileSmile

Maintainence of Replication

Hi Dear...

I have some questions regarding replication in SQL Server 2005.

1. Is it neccessary to have same schema on each side i.e on subsicriber and on publisher?

2. Do replication helps me to replicate the changed schema (of published articals) to the subscribers?

3. If a UDT is defined on publisher and one of its dependent is selected for publication do i need to define the UDT on subscriber manually or it will automatically done for me?

4. pls anyone who can give me the detail known issues and their alternative solutions in regard of maintainence of Replication.

Regards

Mubashar Ahmad

1. Subscriber can have a either the full table, a portion of the table or not at all. You cannot replicate to a totally different schema though.

2. Yes it will replicate ALTER statements.

3. I think you have to do that manaully. However you can set a script to run before the snapshot to create it for you automatically.

4. I dont think anyone can give you that.

Martin

|||

For #3 you have options, see @.schema_option for sp_addarticle.

|||thanks both of you... i ll keep this in mind when i come back to replication.. at the moment i am on long vacations... SmileSmile

Maintainence of Replication

Hi Dear...

I have some questions regarding replication in SQL Server 2005.

1. Is it neccessary to have same schema on each side i.e on subsicriber and on publisher?

2. Do replication helps me to replicate the changed schema (of published articals) to the subscribers?

3. If a UDT is defined on publisher and one of its dependent is selected for publication do i need to define the UDT on subscriber manually or it will automatically done for me?

4. pls anyone who can give me the detail known issues and their alternative solutions in regard of maintainence of Replication.

Regards

Mubashar Ahmad

1. Subscriber can have a either the full table, a portion of the table or not at all. You cannot replicate to a totally different schema though.

2. Yes it will replicate ALTER statements.

3. I think you have to do that manaully. However you can set a script to run before the snapshot to create it for you automatically.

4. I dont think anyone can give you that.

Martin

|||

For #3 you have options, see @.schema_option for sp_addarticle.

|||thanks both of you... i ll keep this in mind when i come back to replication.. at the moment i am on long vacations... SmileSmile

Monday, March 12, 2012

Main requirements per A-A model

Dear all,
I would like to build an Active-Active model with two nodes (Win200 AdServer)
question is easy: which are the most important parameters as well as little
things that then are so important when everything is running in production?
Same memory for both?
Same processor type for both?
Thanks a lot for your response.
Regards,
To make sure that the cluster that you will build will be "Highly Available", the most important thing is to make sure that it is "HCL or WSC-compliant cluster "
Additional Information
===================
The Microsoft support policy for server clusters, the Hardware Compatibility List, and the Windows Server Catalog
http://support.microsoft.com/default...b;en-us;309395
The Microsoft support policy for a SQL Server failover cluster
http://support.microsoft.com/default...b;en-us;327518
Network-Attached Storage and Server Cluster Support
http://support.microsoft.com/default...b;en-us;812504
Once you have a HCL or WSC-Compliant cluster, then the following Microsoft whitepaper will be helpful
Step-by-Step Guide to Installing Windows 2000 Cluster Service
http://www.microsoft.com/windows2000...ustersteps.asp
Step-by-Step Guide to Installing SQL Server 2000 Failover Clustering
http://www.microsoft.com/technet/pro.../failclus.mspx
--> This whitepaper helps with your design of single instance cluster (replaces A/P terminology) or multiple instance cluster (replaces A/A terminology) and helps you determine how much processor, memory, etc
will be required.
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Here is a post that I had recently written for a similar qs.
With instances in SQL Server 2000, come two new concepts for failover clustering:
* Single instance cluster: replaces an active/passive cluster. A single instance cluster means there is one SQL Server 2000 virtual server installed.
* Multiple instance cluster: replaces an active/active cluster. A multiple instance cluster is one in which there is more than one SQL Server 2000 virtual server installed. Because of the way the implementation of
clustering is different with SQL Server 2000, using the active/active terminology does not really apply.
Here is some info that you may find helpful
Single-Instance Cluster
A single-instance cluster has only one active instance of SQL Server owned by a single server node, and all other nodes of the cluster are in a wait state. Another node is enabled in the event of a failure on the
active
node, or during a manual failover for maintenance.
Multiple-Instance Cluster
A multiple-instance cluster has up to four server nodes and supports up to 16 instances (1 default, 15 named or 16 named). Each SQL Server 2000 virtual server requires its own disk resources that cannot be used
by
other instances. These disk resources are the logical drive names (for example, drive F:\) used by SQL Server on which to store data and log files. Separate physical disk sets are needed to make up the logical
drive, unless your disk subsystem supports multiple logical drives on one physical drive set. SQL Server in a clustered environment also behaves differently from a stand-alone named instance in relation to IP
ports.
During the installation process, a dynamic port that may be something other than 1433 is configured, and that port number is reserved for the instance.
For additional information, refer to
Microsoft Whitepaper - SQL Server 2000 Failover Clustering
http://www.microsoft.com/technet/pro.../failclus.mspx
Specifically read the following sections in the whitepaper
* Memory Configuration
-This section presents considerations for memory usage in a SQL Server 2000 failover cluster.
* Processor Capacity
* Using More Than Two Nodes
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Thanks a lot Uttam,
"Uttam Parui[MS]" wrote:

> Here is a post that I had recently written for a similar qs.
>
> With instances in SQL Server 2000, come two new concepts for failover clustering:
> * Single instance cluster: replaces an active/passive cluster. A single instance cluster means there is one SQL Server 2000 virtual server installed.
> * Multiple instance cluster: replaces an active/active cluster. A multiple instance cluster is one in which there is more than one SQL Server 2000 virtual server installed. Because of the way the implementation of
> clustering is different with SQL Server 2000, using the active/active terminology does not really apply.
> Here is some info that you may find helpful
> Single-Instance Cluster
> A single-instance cluster has only one active instance of SQL Server owned by a single server node, and all other nodes of the cluster are in a wait state. Another node is enabled in the event of a failure on the
> active
> node, or during a manual failover for maintenance.
> Multiple-Instance Cluster
> A multiple-instance cluster has up to four server nodes and supports up to 16 instances (1 default, 15 named or 16 named). Each SQL Server 2000 virtual server requires its own disk resources that cannot be used
> by
> other instances. These disk resources are the logical drive names (for example, drive F:\) used by SQL Server on which to store data and log files. Separate physical disk sets are needed to make up the logical
> drive, unless your disk subsystem supports multiple logical drives on one physical drive set. SQL Server in a clustered environment also behaves differently from a stand-alone named instance in relation to IP
> ports.
> During the installation process, a dynamic port that may be something other than 1433 is configured, and that port number is reserved for the instance.
> For additional information, refer to
> Microsoft Whitepaper - SQL Server 2000 Failover Clustering
> http://www.microsoft.com/technet/pro.../failclus.mspx
> Specifically read the following sections in the whitepaper
> * Memory Configuration
> -This section presents considerations for memory usage in a SQL Server 2000 failover cluster.
> * Processor Capacity
> * Using More Than Two Nodes
>
> HTH,
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
>

Wednesday, March 7, 2012

Mail notification to admin for conflicts

Dear Friends
Can it be possible that i get email for the conflict as
and when they appear.
Your guiaence will be helpful to solve my problem.
Best regards
Sharad
with windows synchronization manager if you select interactive resolver you
will get a dialog that pops up on the client notifiying them of a resolution
and they can solve it there.
Other than that you will have to code something yourself.
You might also want to look at the Microsoft SQL Conflict Resolver library.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Sharad" <niitmalad@.yahoo.co.in> wrote in message
news:0b7301c4ec1e$8b4c3d60$a301280a@.phx.gbl...
> Dear Friends
> Can it be possible that i get email for the conflict as
> and when they appear.
> Your guiaence will be helpful to solve my problem.
> Best regards
> Sharad