ability to use variables in package configurations and set their values at runtime

Hi,

My scenario:

I am using a FTP Connection Manager and the configuration setting for it is being set in the package configuration xml file. So the xml file contains the Ftpserver, FTp server username and password. The package is picking up the values from the xml file and is executing successfully. I have to do this because I was not able to provide an expression to the Connection Manager Server Password property.

Now, I want to pick up the ftp details from a database table and set it in the xml file during runtime. Is this possible? OR something like using the

<Configuration ConfiguredType="Property" Path="\Package.Connections[FTP Connection Manager].Properties[ServerPassword]" ValueType="Variable"><ConfiguredValue>@.[user::FtpPassword]</ConfiguredValue></Configuration>

Kindly look at the items in bold. Is this possible? Then I can set the value of the variable in the package before the FTP connection manager task is executed.

Thanks for all the help.

$wapnil

You could use a configuration storage as DB.

Or you can use Script task to query the DB and set the FTP connection properties or Variable values at runtime

Or even Execute SQL task to get the variable values from DB|||

Thanks

Reply to the options that you have provided

1) We want to use XML for the configuration. Just something which we want to follow if we could.

2) We are trying to minimuize the script tasks in the package by bringing the configuration details outside of the package and storing it in XML.

3) same as 1

Lets take a FTP connection Manager for example. The details of the FTP server are present in the database and I have also created variables for that but atleast I am not able to set the FTP Server password using a variable so I resorted to using the xml file and putting in the password there.

Now if I want to connect to multiple FTP server using the same package and the connection details are there in the database then I can pull out the connection details using an Execute SQL task but then how to update the xml files with values......knowing that the FTP server password can be only be set dynamically using the xml file.

Correct me if I am wrong. is storing the variable in the DB the only solution.

Thanks,

$wapnil

|||

spattewar wrote:

Now if I want to connect to multiple FTP server using the same package and the connection details

Are you trying to connect multiple FTP servers at the same time or are you trying to run the package in different environments?

For example if I would need to pull info from 3 different FTP servers - I would create 3 different configuration files:
1 for Development
1 for staging
and 1 for Production site|||

I am trying to connect to multiple FTP servers. But it can be at the same time or in sequence. But I am planning to use a single package for this task.

Thanks for your response.

$wapnil

|||Why don't you use Parent Package Configurations instead? A simple 2-package setup could work where:
Your mother package cycles through a list of FTP server configurations or whatever is needed.|||

That looks like a good idea.

But there is one concern. Even though I pass the configuration as a parent package variable to the child package, will I be able to set the FTP ServerPassword property of the FTP connection manager using a variable. I doubt I can do that, then it boils down to the same thing picking up the package configuration from the xml file or a database, here we would prefer xml file.

Maybe we can do this by.

1) Running the master package which will have a script task to update a xml configuration file.

2) Pass that xml file as a configuration parameter to the child package and execute the child package.

Thanks for your response.

$wapnil

|||I don't have any reason to believe that you can't pass the password or even the whole connectionstring as a variable.

However do note that if your variable values refuse to change (although I don't see any reason why they won't) you might have to tweak the ProtectionLevel of the package to DontSaveSensitive or some other value that allows you to modify your connectionstring variable.

HTHsql

A transport-level error has occurred when receiving results from S

I am setting up a replication of a database which has 364 tables. The size of
this database is close to 150 GB.
I have one server as publisher.
I have another server which i am using for distributor as well as
subscriber. Both servers are seperate physical servers.
I tried replicating 2 tables, I don;' see any issue. They replicate with no
issue. However, when I try to replicate all tables I get this error on
snapshot agent.
Please advise if any one has already seen this problem. My both servers are
on SQL 2005 SP2.
Error messages:
Message: A transport-level error has occurred when receiving results from
the server. (provider: TCP Provider, error: 0 - The specified network name is
no longer available.)
Command Text:
set nocount on
declare @.source_object_id int
declare @.sync_object_id int
set @.source_object_id = object_id(quotename(@.source_object_schema) + N'.' +
quotename(@.source_object_name))
set @.sync_object_id = object_id(quotename(@.sync_object_schema) + N'.' +
quotename(@.sync_object_name))
declare @.partitioning_column sysname
declare @.partitioning_column_type sysname
declare @.qualified_source_object_name nvarchar(600)
declare @.partitioning_column_collation sysname
declare @.partitioning_index_name sysname
set @.qualified_source_object_name = quotename(@.source_object_schema) + N'.'
+ quotename(@.source_object_name)
set @.partitioning_column = null
set @.partitioning_column_type = null
set @.partitioning_index_name = null
select @.partitioning_column = sc.name,
@.partitioning_column_type = st.name,
@.partitioning_column_collation = sc.collation,
@.partitioning_index_name = si.name
from sysindexes si
inner join syscolumns sc
on index_col(@.qualified_source_object_name, si.indid, 1) = sc.name
inner join systypes st
on sc.xtype = st.xusertype
where si.id = @.source_object_id
and sc.id = @.sync_object_id
and si.indid = 1
and st.name in (N'uniqueidentifier', N'bit', N'tinyint', N'smallint',
N'int', N'smalldatetime', N'real', N'money', N'datetime', N'float', N'bit',
N'decimal', N'numeric', N'smallmoney', N'bigint', N'varbinary', N'varchar',
N'binary', N'char', N'timestamp', N'nvarchar', N'nchar')
and (@.use_primary_key_only = 0 or si.status & 2048 = 2048)
if @.partitioning_column is not null
begin
select @.partitioning_index_name, @.partitioning_column,
@.partitioning_column_type, @.partitioning_column_collation
dbcc show_statistics(@.qualified_source_object_name,
@.partitioning_index_name)
end
Parameters: @.source_object_name = E_QRTZ_TRIGGER_LISTENERS
@.source_object_schema = dbo
@.sync_object_name = syncobj_0x3238314643373630
@.sync_object_schema = dbo
@.use_primary_key_only = 1
Stack: at
Microsoft.SqlServer.Replication.AgentCore.ReMapSql Exception(SqlException e,
SqlCommand command)
at
Microsoft.SqlServer.Replication.AgentCore.AgentExe cuteReader(SqlCommand
command, Int32 queryTimeout, CommandBehavior commandBehavior)
at
Microsoft.SqlServer.Replication.AgentCore.ExecuteW ithOptionalResults(CommandSetupDelegate
commandSetupDelegate, ProcessResultsDelegate processResultsDelegate, Int32
queryTimeout, CommandBehavior commandBehavior)
at
Microsoft.SqlServer.Replication.AgentCore.ExecuteW ithOptionalResults(CommandSetupDelegate
commandSetupDelegate, ProcessResultsDelegate processResultsDelegate)
at
Microsoft.SqlServer.Replication.Snapshot.SqlServer .ArticleBcpPartitioningResolver.GatherBaseTableSta tistics()
at
Microsoft.SqlServer.Replication.Snapshot.SqlServer .ArticleBcpPartitioningResolver.ResolveArticleBcpP artitioningUsingKeyDistributionHistogram(BaseArtic leWrapper article, Boolean usePrimaryKeyOnly)
at
Microsoft.SqlServer.Replication.Snapshot.SqlServer .ArticleBcpPartitioningResolver.ResolveArticleBcpP artitioning(BaseArticleWrapper
article, Boolean usePrimaryKeyOnly)
at
Microsoft.SqlServer.Replication.Snapshot.SqlServer .BcpLoadHintAndPartitioningResolutionWorkerThreadP rovider.DoWork(WorkItem workItem)
at
Microsoft.SqlServer.Replication.WorkerThread.NonEx ceptionBasedAgentThreadProc()
at Microsoft.SqlServer.Replication.WorkerThread.Agent ThreadProc()
at
Microsoft.SqlServer.Replication.AgentCore.BaseAgen tThread.AgentThreadProcWrapper() (Source: MSSQLServer, Error number: 64)
Get help: http://help/64
Server NTFWEPSQLT1, Level 20, State 0, Line 0
A transport-level error has occurred when receiving results from the server.
(provider: TCP Provider, error: 0 - The specified network name is no longer
available.) (Source: MSSQLServer, Error number: 64)
Get help: http://help/64
Sr DBA
Pier 1 Imports
mabbas@.Pier1.com
You had a network failure in the middle of your snapshot distribution. This
should clear the next time it runs. You might want to run ping -t to watch
to see how lossy your link is.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Moh" <mabbas@.Pier1.com> wrote in message
news:B877BD9F-EE3C-456E-87A7-64BB17FC5C11@.microsoft.com...
>I am setting up a replication of a database which has 364 tables. The size
>of
> this database is close to 150 GB.
> I have one server as publisher.
> I have another server which i am using for distributor as well as
> subscriber. Both servers are seperate physical servers.
> I tried replicating 2 tables, I don;' see any issue. They replicate with
> no
> issue. However, when I try to replicate all tables I get this error on
> snapshot agent.
> Please advise if any one has already seen this problem. My both servers
> are
> on SQL 2005 SP2.
> --
> Error messages:
> Message: A transport-level error has occurred when receiving results from
> the server. (provider: TCP Provider, error: 0 - The specified network name
> is
> no longer available.)
> Command Text:
> set nocount on
> declare @.source_object_id int
> declare @.sync_object_id int
> set @.source_object_id = object_id(quotename(@.source_object_schema) + N'.'
> +
> quotename(@.source_object_name))
> set @.sync_object_id = object_id(quotename(@.sync_object_schema) + N'.' +
> quotename(@.sync_object_name))
> declare @.partitioning_column sysname
> declare @.partitioning_column_type sysname
> declare @.qualified_source_object_name nvarchar(600)
> declare @.partitioning_column_collation sysname
> declare @.partitioning_index_name sysname
> set @.qualified_source_object_name = quotename(@.source_object_schema) +
> N'.'
> + quotename(@.source_object_name)
> set @.partitioning_column = null
> set @.partitioning_column_type = null
> set @.partitioning_index_name = null
> select @.partitioning_column = sc.name,
> @.partitioning_column_type = st.name,
> @.partitioning_column_collation = sc.collation,
> @.partitioning_index_name = si.name
> from sysindexes si
> inner join syscolumns sc
> on index_col(@.qualified_source_object_name, si.indid, 1) = sc.name
> inner join systypes st
> on sc.xtype = st.xusertype
> where si.id = @.source_object_id
> and sc.id = @.sync_object_id
> and si.indid = 1
> and st.name in (N'uniqueidentifier', N'bit', N'tinyint',
> N'smallint',
> N'int', N'smalldatetime', N'real', N'money', N'datetime', N'float',
> N'bit',
> N'decimal', N'numeric', N'smallmoney', N'bigint', N'varbinary',
> N'varchar',
> N'binary', N'char', N'timestamp', N'nvarchar', N'nchar')
> and (@.use_primary_key_only = 0 or si.status & 2048 = 2048)
> if @.partitioning_column is not null
> begin
> select @.partitioning_index_name, @.partitioning_column,
> @.partitioning_column_type, @.partitioning_column_collation
> dbcc show_statistics(@.qualified_source_object_name,
> @.partitioning_index_name)
> end
> Parameters: @.source_object_name = E_QRTZ_TRIGGER_LISTENERS
> @.source_object_schema = dbo
> @.sync_object_name = syncobj_0x3238314643373630
> @.sync_object_schema = dbo
> @.use_primary_key_only = 1
> Stack: at
> Microsoft.SqlServer.Replication.AgentCore.ReMapSql Exception(SqlException
> e,
> SqlCommand command)
> at
> Microsoft.SqlServer.Replication.AgentCore.AgentExe cuteReader(SqlCommand
> command, Int32 queryTimeout, CommandBehavior commandBehavior)
> at
> Microsoft.SqlServer.Replication.AgentCore.ExecuteW ithOptionalResults(CommandSetupDelegate
> commandSetupDelegate, ProcessResultsDelegate processResultsDelegate, Int32
> queryTimeout, CommandBehavior commandBehavior)
> at
> Microsoft.SqlServer.Replication.AgentCore.ExecuteW ithOptionalResults(CommandSetupDelegate
> commandSetupDelegate, ProcessResultsDelegate processResultsDelegate)
> at
> Microsoft.SqlServer.Replication.Snapshot.SqlServer .ArticleBcpPartitioningResolver.GatherBaseTableSta tistics()
> at
> Microsoft.SqlServer.Replication.Snapshot.SqlServer .ArticleBcpPartitioningResolver.ResolveArticleBcpP artitioningUsingKeyDistributionHistogram(BaseArtic leWrapper
> article, Boolean usePrimaryKeyOnly)
> at
> Microsoft.SqlServer.Replication.Snapshot.SqlServer .ArticleBcpPartitioningResolver.ResolveArticleBcpP artitioning(BaseArticleWrapper
> article, Boolean usePrimaryKeyOnly)
> at
> Microsoft.SqlServer.Replication.Snapshot.SqlServer .BcpLoadHintAndPartitioningResolutionWorkerThreadP rovider.DoWork(WorkItem
> workItem)
> at
> Microsoft.SqlServer.Replication.WorkerThread.NonEx ceptionBasedAgentThreadProc()
> at Microsoft.SqlServer.Replication.WorkerThread.Agent ThreadProc()
> at
> Microsoft.SqlServer.Replication.AgentCore.BaseAgen tThread.AgentThreadProcWrapper()
> (Source: MSSQLServer, Error number: 64)
> Get help: http://help/64
> Server NTFWEPSQLT1, Level 20, State 0, Line 0
> A transport-level error has occurred when receiving results from the
> server.
> (provider: TCP Provider, error: 0 - The specified network name is no
> longer
> available.) (Source: MSSQLServer, Error number: 64)
> Get help: http://help/64
> --
> Sr DBA
> Pier 1 Imports
> mabbas@.Pier1.com
|||Hilary - Why then it always works when I replicate any small database or same
data base with few articles. I see no time outs when ping during replication.
Sr DBA
Pier 1 Imports
mabbas@.Pier1.com
"Hilary Cotter" wrote:

> You had a network failure in the middle of your snapshot distribution. This
> should clear the next time it runs. You might want to run ping -t to watch
> to see how lossy your link is.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Moh" <mabbas@.Pier1.com> wrote in message
> news:B877BD9F-EE3C-456E-87A7-64BB17FC5C11@.microsoft.com...
>
>
|||It really looks like a network failure somewhere. The ping-t command should
reveal network hiccups occurring during the snapshot application.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Moh" <mabbas@.Pier1.com> wrote in message
news:C3B863FA-723D-4781-9A99-99FCA2DDB364@.microsoft.com...[vbcol=seagreen]
> Hilary - Why then it always works when I replicate any small database or
> same
> data base with few articles. I see no time outs when ping during
> replication.
> --
> Sr DBA
> Pier 1 Imports
> mabbas@.Pier1.com
>
> "Hilary Cotter" wrote:
|||Actually, the SQL Server could think it's under a DOS attack and start
killing off connections.
Check out section 5.1 of
http://download.microsoft.com/download/f/1/0/f10c4f60-630e-4153-bd53-c3010e4c513b/ReadmeSQLEXP2005.htm#sse_dbengine
for more information.
On Mar 19, 1:02 pm, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
> It really looks like a network failure somewhere. The ping-t command should
> reveal network hiccups occurring during the snapshot application.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com
> "Moh" <mab...@.Pier1.com> wrote in message
> news:C3B863FA-723D-4781-9A99-99FCA2DDB364@.microsoft.com...
>
>
>
>
>
>
>
>
>
> - Show quoted text -

A problem with polish Chars.

Hi guys,

I got a big problem with my SQL 2000 DB, I got to enter polish chars in the fields and I don't seem to be able to. I tried setting the collation to SQL_Latin1_General_CP1250_CI_AS or SQL_Polish_CP1250_CS_AS or used the window collation in polish on the separate fields, I tried setting my new DB collation to SQL_Polish_CP1250_CI_AS. But nothing helped I tried to insert the phrase "Wyda?e? 200 punktów na gr? w ping-ponga." but every time the special chars like the "?" or the "ó" are gone and become normal "e" or "o".

Could somebody help me here cause I'm really not getting out of this one.

Hi!

Posted elsewhere by Dejan Sarka, SQL Server MVP :

"In SQL 2000 you can define collations on server, db and column level. This collation is used, for example if defined on column level for a varchar column, on all rows. If you need different collations in different rows of the same column, then you have to use unicode data types, in the example nvarchar. So, check the collation on all levels - server, db and column."

A problem with polish Chars.

Hi guys,

I got a big problem with my SQL 2000 DB, I got to enter polish chars in the fields and I don't seem to be able to. I tried setting the collation to SQL_Latin1_General_CP1250_CI_AS or SQL_Polish_CP1250_CS_AS or used the window collation in polish on the separate fields, I tried setting my new DB collation to SQL_Polish_CP1250_CI_AS. But nothing helped I tried to insert the phrase "Wyda?e? 200 punktów na gr? w ping-ponga." but every time the special chars like the "?" or the "ó" are gone and become normal "e" or "o".

Could somebody help me here cause I'm really not getting out of this one.

Hi!

Posted elsewhere by Dejan Sarka, SQL Server MVP :

"In SQL 2000 you can define collations on server, db and column level. This collation is used, for example if defined on column level for a varchar column, on all rows. If you need different collations in different rows of the same column, then you have to use unicode data types, in the example nvarchar. So, check the collation on all levels - server, db and column."

A few questions: Clustering & Replication

Hi,
In SQL 2005, with SQL Clustering:
1. Can a THREE-node active/active/active cluster be setup? If yes, is
setting up a three-node a/a/a cluster recommended? Any pitfalls or gotchas
that one needs to be aware of?
With Replication:
1. Can a subscriber in turn be a publisher to another subscriber? i.e. a
subscriber subsribes to a publication from one publisher and then in turn
creates a similar publication, which is subscribed by another subscriber.
2. Can replication (immediate and/or queued updating) be configured between
THREE servers? i.e. each server is a publisher and subcriber to the other two
servers.
We are working on a global strategy to identify how best to keep data in
sync between three geographically located SQL servers, while maintaining
latency as low as possible.
Peer-to-Peer replication was investigated as well, but it did not fit with
our company's strategic plan as one of our requirement is that database
updates can be done at any server, at anytime. Peer-to-Peer allows updates
for a given row only at one database until it has been syncronized with its
peers, which can be done by directing updates for a set of rows to a
particular server.
Your guidance, thougths, and suggestions are very valued and appreciated.
TIA
Regards,<DIV>"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:7C72EA17-1D74-42FA-BA28-6A0CBDC5535C@.microsoft.com...</DIV>> Hi,
> In SQL 2005, with SQL Clustering:
> 1. Can a THREE-node active/active/active cluster be setup? If yes, is
> setting up a three-node a/a/a cluster recommended? Any pitfalls or gotchas
> that one needs to be aware of?
Yes, although we don't really call it active/active anymore. It's just an
N-node cluster. It has a number of cluster nodes and a number of SQL
instances (virtual servers). The biggest problem with running SQL instances
on all your cluster nodes is that you can have performance problems when you
fail over. Often you add an extra passive node to hold enough capacity in
reserve for failover. This is generally referred to as an N+1 cluster (N
"active" nodes, 1 "passive").
> With Replication:
> 1. Can a subscriber in turn be a publisher to another subscriber? i.e. a
> subscriber subsribes to a publication from one publisher and then in turn
> creates a similar publication, which is subscribed by another subscriber.
> 2. Can replication (immediate and/or queued updating) be configured
> between
> THREE servers? i.e. each server is a publisher and subcriber to the other
> two
> servers.
> We are working on a global strategy to identify how best to keep data in
> sync between three geographically located SQL servers, while maintaining
> latency as low as possible.
> Peer-to-Peer replication was investigated as well, but it did not fit with
> our company's strategic plan as one of our requirement is that database
> updates can be done at any server, at anytime. Peer-to-Peer allows updates
> for a given row only at one database until it has been syncronized with
> its
> peers, which can be done by directing updates for a set of rows to a
> particular server.
You've got it wrong with Peer-to-Peer. Peer-to-Peer allows update to any
server at anytime. It just has no mechanism to protect you if you make
conflicting changes at nearly the same time, one of the changes will be
lost. The situation you are describing with multiple publishers would
behave in a similar manner.
David|||1) Yes, the gotcha is that at any one time a node may have to support all
three instances which means it will have to be pretty beefy to offer optimal
performance to all three instances
Replication
1) Yes, its called republishing. It normally used to provide hierarchies in
merge replication to scale out.
2) No, but you might want to look at bi-directional transactional
replication which can be used to do this. It would provide bi-directional
replication between node a and node b, and node a and node c, but not
between node b and node c unless you implement some pretty complex
filtering.
When Peer to peer out of the box encounters an error its distribution agents
will stop until you fix the error. You can run it in the continue on data
consistency errors profile, but doing this will leave your databases in an
inconsistent state.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:7C72EA17-1D74-42FA-BA28-6A0CBDC5535C@.microsoft.com...
> Hi,
> In SQL 2005, with SQL Clustering:
> 1. Can a THREE-node active/active/active cluster be setup? If yes, is
> setting up a three-node a/a/a cluster recommended? Any pitfalls or gotchas
> that one needs to be aware of?
> With Replication:
> 1. Can a subscriber in turn be a publisher to another subscriber? i.e. a
> subscriber subsribes to a publication from one publisher and then in turn
> creates a similar publication, which is subscribed by another subscriber.
> 2. Can replication (immediate and/or queued updating) be configured
> between
> THREE servers? i.e. each server is a publisher and subcriber to the other
> two
> servers.
> We are working on a global strategy to identify how best to keep data in
> sync between three geographically located SQL servers, while maintaining
> latency as low as possible.
> Peer-to-Peer replication was investigated as well, but it did not fit with
> our company's strategic plan as one of our requirement is that database
> updates can be done at any server, at anytime. Peer-to-Peer allows updates
> for a given row only at one database until it has been syncronized with
> its
> peers, which can be done by directing updates for a set of rows to a
> particular server.
> Your guidance, thougths, and suggestions are very valued and appreciated.
> TIA
> Regards,|||Hi Rob,
the only thing I'd add to the other comments is that merge replication
essentially covers point (2). The terminology is in conflict but the
functionality is the same ie there would only be need for one publisher, and
the pthers would be subscribers, but for the most part, there isn't a
distinction between these roles in merge replication.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com|||Thanks Hilary.
For replication Q. 2: You may have already answered this but I was wondering
if a bi-directional replication were to exists between node A and B, could
node B republish the data to node C unidirectionally?
Regards,
- Rob.
"Hilary Cotter" wrote:
> 1) Yes, the gotcha is that at any one time a node may have to support all
> three instances which means it will have to be pretty beefy to offer optimal
> performance to all three instances
> Replication
> 1) Yes, its called republishing. It normally used to provide hierarchies in
> merge replication to scale out.
> 2) No, but you might want to look at bi-directional transactional
> replication which can be used to do this. It would provide bi-directional
> replication between node a and node b, and node a and node c, but not
> between node b and node c unless you implement some pretty complex
> filtering.
> When Peer to peer out of the box encounters an error its distribution agents
> will stop until you fix the error. You can run it in the continue on data
> consistency errors profile, but doing this will leave your databases in an
> inconsistent state.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Rob" <Rob@.discussions.microsoft.com> wrote in message
> news:7C72EA17-1D74-42FA-BA28-6A0CBDC5535C@.microsoft.com...
> > Hi,
> >
> > In SQL 2005, with SQL Clustering:
> > 1. Can a THREE-node active/active/active cluster be setup? If yes, is
> > setting up a three-node a/a/a cluster recommended? Any pitfalls or gotchas
> > that one needs to be aware of?
> >
> > With Replication:
> > 1. Can a subscriber in turn be a publisher to another subscriber? i.e. a
> > subscriber subsribes to a publication from one publisher and then in turn
> > creates a similar publication, which is subscribed by another subscriber.
> > 2. Can replication (immediate and/or queued updating) be configured
> > between
> > THREE servers? i.e. each server is a publisher and subcriber to the other
> > two
> > servers.
> >
> > We are working on a global strategy to identify how best to keep data in
> > sync between three geographically located SQL servers, while maintaining
> > latency as low as possible.
> >
> > Peer-to-Peer replication was investigated as well, but it did not fit with
> > our company's strategic plan as one of our requirement is that database
> > updates can be done at any server, at anytime. Peer-to-Peer allows updates
> > for a given row only at one database until it has been syncronized with
> > its
> > peers, which can be done by directing updates for a set of rows to a
> > particular server.
> >
> > Your guidance, thougths, and suggestions are very valued and appreciated.
> >
> > TIA
> >
> > Regards,
>
>