Dear Professional,

I would highly appreciate if you can guide me for my one problem, I have two
servers and I want to create link server. One is at Canada and other one is
at USA. Now the problem is that both are not on domain and I am wondering
about performance. I might to update the information if happend on Canada
box to USA box. Now the question is SP_ADDLINKEDSERVER is a good option to
do this? In which box I have to create Linked Server Canada Box or USA Box?
this should be real time update, how about performance? any thing I have to
take care before creating linked server on the production box?

Thanks

Noor,

Canada and USA servers are linked in what way, what is your line speed
between the servers, et cetera.

Unless the communication is pretty fast, I doubt that you want to use a
distributed transaction to keep the two servers in sychronization. And, even
if it is fast it can go down. Do you want one server to be locked up
waiting for the other to respond? I would not recommend that kind of
dependency between remote servers.

I would suggest that you read about replication to see if that serves your
needs. If you want updates to flow both directions, then read about merge
replication. Here is a link to some replication tuturials:
http://msdn2.microsoft.com/en-us/library/aa337389.aspx

If you pursue replication as a strategy, you can post additional questions
at: microsoft.public.sqlserver.replication


RLF

"Noor" <naissani (AT) hotmail (DOT) com> wrote

Noor,

Canada and USA servers are linked in what way, what is your line speed
between the servers, et cetera.

Unless the communication is pretty fast, I doubt that you want to use a
distributed transaction to keep the two servers in sychronization. And, even
if it is fast it can go down. Do you want one server to be locked up
waiting for the other to respond? I would not recommend that kind of
dependency between remote servers.

I would suggest that you read about replication to see if that serves your
needs. If you want updates to flow both directions, then read about merge
replication. Here is a link to some replication tuturials:
http://msdn2.microsoft.com/en-us/library/aa337389.aspx

If you pursue replication as a strategy, you can post additional questions
at: microsoft.public.sqlserver.replication


RLF

"Noor" <naissani (AT) hotmail (DOT) com> wrote

Noor,

Canada and USA servers are linked in what way, what is your line speed
between the servers, et cetera.

Unless the communication is pretty fast, I doubt that you want to use a
distributed transaction to keep the two servers in sychronization. And, even
if it is fast it can go down. Do you want one server to be locked up
waiting for the other to respond? I would not recommend that kind of
dependency between remote servers.

I would suggest that you read about replication to see if that serves your
needs. If you want updates to flow both directions, then read about merge
replication. Here is a link to some replication tuturials:
http://msdn2.microsoft.com/en-us/library/aa337389.aspx

If you pursue replication as a strategy, you can post additional questions
at: microsoft.public.sqlserver.replication


RLF

"Noor" <naissani (AT) hotmail (DOT) com> wrote

Noor,

Canada and USA servers are linked in what way, what is your line speed
between the servers, et cetera.

Unless the communication is pretty fast, I doubt that you want to use a
distributed transaction to keep the two servers in sychronization. And, even
if it is fast it can go down. Do you want one server to be locked up
waiting for the other to respond? I would not recommend that kind of
dependency between remote servers.

I would suggest that you read about replication to see if that serves your
needs. If you want updates to flow both directions, then read about merge
replication. Here is a link to some replication tuturials:
http://msdn2.microsoft.com/en-us/library/aa337389.aspx

If you pursue replication as a strategy, you can post additional questions
at: microsoft.public.sqlserver.replication


RLF

"Noor" <naissani (AT) hotmail (DOT) com> wrote

Noor,

Canada and USA servers are linked in what way, what is your line speed
between the servers, et cetera.

Unless the communication is pretty fast, I doubt that you want to use a
distributed transaction to keep the two servers in sychronization. And, even
if it is fast it can go down. Do you want one server to be locked up
waiting for the other to respond? I would not recommend that kind of
dependency between remote servers.

I would suggest that you read about replication to see if that serves your
needs. If you want updates to flow both directions, then read about merge
replication. Here is a link to some replication tuturials:
http://msdn2.microsoft.com/en-us/library/aa337389.aspx

If you pursue replication as a strategy, you can post additional questions
at: microsoft.public.sqlserver.replication


RLF

"Noor" <naissani (AT) hotmail (DOT) com> wrote

Noor,

Canada and USA servers are linked in what way, what is your line speed
between the servers, et cetera.

Unless the communication is pretty fast, I doubt that you want to use a
distributed transaction to keep the two servers in sychronization. And, even
if it is fast it can go down. Do you want one server to be locked up
waiting for the other to respond? I would not recommend that kind of
dependency between remote servers.

I would suggest that you read about replication to see if that serves your
needs. If you want updates to flow both directions, then read about merge
replication. Here is a link to some replication tuturials:
http://msdn2.microsoft.com/en-us/library/aa337389.aspx

If you pursue replication as a strategy, you can post additional questions
at: microsoft.public.sqlserver.replication


RLF

"Noor" <naissani (AT) hotmail (DOT) com> wrote

Noor,

Canada and USA servers are linked in what way, what is your line speed
between the servers, et cetera.

Unless the communication is pretty fast, I doubt that you want to use a
distributed transaction to keep the two servers in sychronization. And, even
if it is fast it can go down. Do you want one server to be locked up
waiting for the other to respond? I would not recommend that kind of
dependency between remote servers.

I would suggest that you read about replication to see if that serves your
needs. If you want updates to flow both directions, then read about merge
replication. Here is a link to some replication tuturials:
http://msdn2.microsoft.com/en-us/library/aa337389.aspx

If you pursue replication as a strategy, you can post additional questions
at: microsoft.public.sqlserver.replication


RLF

"Noor" <naissani (AT) hotmail (DOT) com> wrote

Noor,

Canada and USA servers are linked in what way, what is your line speed
between the servers, et cetera.

Unless the communication is pretty fast, I doubt that you want to use a
distributed transaction to keep the two servers in sychronization. And, even
if it is fast it can go down. Do you want one server to be locked up
waiting for the other to respond? I would not recommend that kind of
dependency between remote servers.

I would suggest that you read about replication to see if that serves your
needs. If you want updates to flow both directions, then read about merge
replication. Here is a link to some replication tuturials:
http://msdn2.microsoft.com/en-us/library/aa337389.aspx

If you pursue replication as a strategy, you can post additional questions
at: microsoft.public.sqlserver.replication


RLF

"Noor" <naissani (AT) hotmail (DOT) com> wrote

Noor,

Canada and USA servers are linked in what way, what is your line speed
between the servers, et cetera.

Unless the communication is pretty fast, I doubt that you want to use a
distributed transaction to keep the two servers in sychronization. And, even
if it is fast it can go down. Do you want one server to be locked up
waiting for the other to respond? I would not recommend that kind of
dependency between remote servers.

I would suggest that you read about replication to see if that serves your
needs. If you want updates to flow both directions, then read about merge
replication. Here is a link to some replication tuturials:
http://msdn2.microsoft.com/en-us/library/aa337389.aspx

If you pursue replication as a strategy, you can post additional questions
at: microsoft.public.sqlserver.replication


RLF

"Noor" <naissani (AT) hotmail (DOT) com> wrote