How to implement Database Mirroring with SQL2000

Hi,
Our client is located in Europe region. Our application was a web based
application using SQL Server 2000 database as the back-end, where this server
was located in Europe region. All the users will visit this site through out
the world.
Now the client was observing some performance problems in their offices in
Asia region. The reason seems to be a relatively bad connection between
Europe and Asia. The available bandwidth should be by far sufficient (10
Mbit/s), but the latency seems to be too slow (approx. 350 ms). Our Client is
checking with other providers, but they may have similar problems. The effect
is that the measured response times in their Asian office are too long
(typically 3 – 5 seconds). Their target is to get response times below 2
seconds to make sure that the users can work efficiently.
One possible solution which has been suggested to us was that to install the
web based application also on a server in the Asian office. There would be 2
mirrored databases with the same data. The users in Asia would access this
server, whereas the users in Europe and America would access the server in
Europe. Probably it would be sufficient to update the data once a day or even
less frequently.
Does SQL Server 2000 support such a solution? Do you think this would be a
feasible solution? If this solution should be implemented, how should we
proceed?
Or else Can you suggest any other solution?
Thanks and Regards
ourspt
ourspt
> Does SQL Server 2000 support such a solution? Do you think this would be a
> feasible solution? If this solution should be implemented, how should we
> proceed?
Yes it does. It could be SNAPSHOT Replication to update tthe database or
just simple BACKUP and RESTORE database
But regarding to where the server should be located it is your decision and
do some testing
http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
Replica (Step by step)
"ourspt" <ourspt@.discussions.microsoft.com> wrote in message
news:BAA5A573-735B-449F-90BD-9DB6A54D3D10@.microsoft.com...
> Hi,
> Our client is located in Europe region. Our application was a web based
> application using SQL Server 2000 database as the back-end, where this
> server
> was located in Europe region. All the users will visit this site through
> out
> the world.
> Now the client was observing some performance problems in their offices in
> Asia region. The reason seems to be a relatively bad connection between
> Europe and Asia. The available bandwidth should be by far sufficient (10
> Mbit/s), but the latency seems to be too slow (approx. 350 ms). Our Client
> is
> checking with other providers, but they may have similar problems. The
> effect
> is that the measured response times in their Asian office are too long
> (typically 3 5 seconds). Their target is to get response times below 2
> seconds to make sure that the users can work efficiently.
> One possible solution which has been suggested to us was that to install
> the
> web based application also on a server in the Asian office. There would be
> 2
> mirrored databases with the same data. The users in Asia would access this
> server, whereas the users in Europe and America would access the server in
> Europe. Probably it would be sufficient to update the data once a day or
> even
> less frequently.
> Does SQL Server 2000 support such a solution? Do you think this would be a
> feasible solution? If this solution should be implemented, how should we
> proceed?
> Or else Can you suggest any other solution?
> Thanks and Regards
> --
> ourspt

How to implement Database Mirroring with SQL2000

Hi,
Our client is located in Europe region. Our application was a web based
application using SQL Server 2000 database as the back-end, where this serve
r
was located in Europe region. All the users will visit this site through out
the world.
Now the client was observing some performance problems in their offices in
Asia region. The reason seems to be a relatively bad connection between
Europe and Asia. The available bandwidth should be by far sufficient (10
Mbit/s), but the latency seems to be too slow (approx. 350 ms). Our Client i
s
checking with other providers, but they may have similar problems. The effec
t
is that the measured response times in their Asian office are too long
(typically 3 – 5 seconds). Their target is to get response times below 2
seconds to make sure that the users can work efficiently.
One possible solution which has been suggested to us was that to install the
web based application also on a server in the Asian office. There would be 2
mirrored databases with the same data. The users in Asia would access this
server, whereas the users in Europe and America would access the server in
Europe. Probably it would be sufficient to update the data once a day or eve
n
less frequently.
Does SQL Server 2000 support such a solution? Do you think this would be a
feasible solution? If this solution should be implemented, how should we
proceed?
Or else Can you suggest any other solution?
Thanks and Regards
--
oursptourspt
> Does SQL Server 2000 support such a solution? Do you think this would be a
> feasible solution? If this solution should be implemented, how should we
> proceed?
Yes it does. It could be SNAPSHOT Replication to update tthe database or
just simple BACKUP and RESTORE database
But regarding to where the server should be located it is your decision and
do some testing
http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
Replica (Step by step)
"ourspt" <ourspt@.discussions.microsoft.com> wrote in message
news:BAA5A573-735B-449F-90BD-9DB6A54D3D10@.microsoft.com...
> Hi,
> Our client is located in Europe region. Our application was a web based
> application using SQL Server 2000 database as the back-end, where this
> server
> was located in Europe region. All the users will visit this site through
> out
> the world.
> Now the client was observing some performance problems in their offices in
> Asia region. The reason seems to be a relatively bad connection between
> Europe and Asia. The available bandwidth should be by far sufficient (10
> Mbit/s), but the latency seems to be too slow (approx. 350 ms). Our Client
> is
> checking with other providers, but they may have similar problems. The
> effect
> is that the measured response times in their Asian office are too long
> (typically 3 5 seconds). Their target is to get response times below 2
> seconds to make sure that the users can work efficiently.
> One possible solution which has been suggested to us was that to install
> the
> web based application also on a server in the Asian office. There would be
> 2
> mirrored databases with the same data. The users in Asia would access this
> server, whereas the users in Europe and America would access the server in
> Europe. Probably it would be sufficient to update the data once a day or
> even
> less frequently.
> Does SQL Server 2000 support such a solution? Do you think this would be a
> feasible solution? If this solution should be implemented, how should we
> proceed?
> Or else Can you suggest any other solution?
> Thanks and Regards
> --
> ourspt

How to implement Database Mirroring with SQL2000

Hi,
Our client is located in Europe region. Our application was a web based
application using SQL Server 2000 database as the back-end, where this server
was located in Europe region. All the users will visit this site through out
the world.
Now the client was observing some performance problems in their offices in
Asia region. The reason seems to be a relatively bad connection between
Europe and Asia. The available bandwidth should be by far sufficient (10
Mbit/s), but the latency seems to be too slow (approx. 350 ms). Our Client is
checking with other providers, but they may have similar problems. The effect
is that the measured response times in their Asian office are too long
(typically 3 â' 5 seconds). Their target is to get response times below 2
seconds to make sure that the users can work efficiently.
One possible solution which has been suggested to us was that to install the
web based application also on a server in the Asian office. There would be 2
mirrored databases with the same data. The users in Asia would access this
server, whereas the users in Europe and America would access the server in
Europe. Probably it would be sufficient to update the data once a day or even
less frequently.
Does SQL Server 2000 support such a solution? Do you think this would be a
feasible solution? If this solution should be implemented, how should we
proceed?
Or else Can you suggest any other solution?
Thanks and Regards
--
oursptourspt
> Does SQL Server 2000 support such a solution? Do you think this would be a
> feasible solution? If this solution should be implemented, how should we
> proceed?
Yes it does. It could be SNAPSHOT Replication to update tthe database or
just simple BACKUP and RESTORE database
But regarding to where the server should be located it is your decision and
do some testing
http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
Replica (Step by step)
"ourspt" <ourspt@.discussions.microsoft.com> wrote in message
news:BAA5A573-735B-449F-90BD-9DB6A54D3D10@.microsoft.com...
> Hi,
> Our client is located in Europe region. Our application was a web based
> application using SQL Server 2000 database as the back-end, where this
> server
> was located in Europe region. All the users will visit this site through
> out
> the world.
> Now the client was observing some performance problems in their offices in
> Asia region. The reason seems to be a relatively bad connection between
> Europe and Asia. The available bandwidth should be by far sufficient (10
> Mbit/s), but the latency seems to be too slow (approx. 350 ms). Our Client
> is
> checking with other providers, but they may have similar problems. The
> effect
> is that the measured response times in their Asian office are too long
> (typically 3 ? 5 seconds). Their target is to get response times below 2
> seconds to make sure that the users can work efficiently.
> One possible solution which has been suggested to us was that to install
> the
> web based application also on a server in the Asian office. There would be
> 2
> mirrored databases with the same data. The users in Asia would access this
> server, whereas the users in Europe and America would access the server in
> Europe. Probably it would be sufficient to update the data once a day or
> even
> less frequently.
> Does SQL Server 2000 support such a solution? Do you think this would be a
> feasible solution? If this solution should be implemented, how should we
> proceed?
> Or else Can you suggest any other solution?
> Thanks and Regards
> --
> ourspt

How to identify IDENTITY column on a linked server table?

Using SQL2000 (latest SP and patches)...
I'm trying to identify the IDENTITY column of a table in a database on a
linked server. Ordinarily I'd just use sp_columns, but since it's a linked
database I have to use sp_columns_ex, and it doesn't return the IDENTITY
column identifier!
Help!! :) Any ideas? Thanks!
JackHave you tried
exec linkerserver.db.dbo.sp_help tablename
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jack Black" <jackblackisback@.hotmail.com> wrote in message
news:%23e438$y0DHA.404@.tk2msftngp13.phx.gbl...
> Using SQL2000 (latest SP and patches)...
> I'm trying to identify the IDENTITY column of a table in a database on a
> linked server. Ordinarily I'd just use sp_columns, but since it's a
linked
> database I have to use sp_columns_ex, and it doesn't return the IDENTITY
> column identifier!
> Help!! :) Any ideas? Thanks!
> Jack
>|||Thanks for responding! :)
Yeah, I've tried that... Suffice to say the scripting language I'm using
(ColdFusion) doesn't support multiple resultsets without using their stored
procedure tag (CFSTOREDPROC), so I would have to build the query into a
stored proc. Normally not a problem, but CFSTOREDPROC is hardwired to
execute all sp's with a call command, so the syntax executed would be "CALL
EXEC ...", resulting in a failed call. And since CALL doesn't work with
linked server syntax, I can't use it.
I'm trying to avoid requiring a local DSN pointing to the remote SQL server,
but I think it's coming down to needing that because of CF's shortcomings...
Any other thoughts welcome!! :)
Jack
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:u2sBBC40DHA.716@.TK2MSFTNGP12.phx.gbl...
> Have you tried
> exec linkerserver.db.dbo.sp_help tablename
>
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Computer Education Services Corporation (CESC), Charlotte, NC
> www.computeredservices.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "Jack Black" <jackblackisback@.hotmail.com> wrote in message
> news:%23e438$y0DHA.404@.tk2msftngp13.phx.gbl...
> > Using SQL2000 (latest SP and patches)...
> >
> > I'm trying to identify the IDENTITY column of a table in a database on a
> > linked server. Ordinarily I'd just use sp_columns, but since it's a
> linked
> > database I have to use sp_columns_ex, and it doesn't return the IDENTITY
> > column identifier!
> >
> > Help!! :) Any ideas? Thanks!
> > Jack
> >
> >
>