Remote to Remote

Hi,

We have 3 database server . one is local and other two are in two different locations.

Scenario is , we have to import a database from one old remote server to another new remote server.
Since, it should be difficult (bcoz of firewall issues) to import from old remote to new remote server, i thought to
import to my local DB server then import database to new remote server.

I am planning to give IMPORT/EXPORT option in the ALL TASKS property, from my local m/c to the old remote server.
then take BACKUP database in my local machine . After that just copy the backup file to my new Remote server and then
just restore it.

Or is there any better solution to accomplish this ?

Please give me some advice !

Thanks,

HadleyWhy not consider using REPLICATION or LOG SHIPPING kind of solution rather depending on roundabout solution. Refer to books online for more information.

Remote SQl connection

I have a SQL server that was formatted and reconfigured. Prior to the
format, I was able to access this server from remote locations by creating a
n
ODBC connection in Administrative Tools in Windows XP. I haven't changed my
firewall or the server IP. As far as I can see, everything should be the
same. The problem now is that I can't create an ODBC connection unless I'm
on my network and a member of the domain. Even if I'm with my network, but
not a member of the domain, I can't create the ODBC connection.
The server is set up using mixed-mode authentication and as I mentioned, I
can create this connection if I'm on the domain. Any suggestions as to why
I
can't do this remotely? Thanks in advance for your help.Hi
Can you see the server (using ping?). Which protocols do you have enabled?
Is the SQL Server on the domain? Have you re-created the users, logins and
trusts to be exactly the same? What error message do you get?
John
"J.B.C" <JBC@.discussions.microsoft.com> wrote in message
news:F9887DA2-34B9-42F2-A903-CBF04CE9DDD7@.microsoft.com...
>I have a SQL server that was formatted and reconfigured. Prior to the
> format, I was able to access this server from remote locations by creating
> an
> ODBC connection in Administrative Tools in Windows XP. I haven't changed
> my
> firewall or the server IP. As far as I can see, everything should be
> the
> same. The problem now is that I can't create an ODBC connection unless
> I'm
> on my network and a member of the domain. Even if I'm with my network,
> but
> not a member of the domain, I can't create the ODBC connection.
> The server is set up using mixed-mode authentication and as I mentioned, I
> can create this connection if I'm on the domain. Any suggestions as to
> why I
> can't do this remotely? Thanks in advance for your help.

Remote SQl connection

I have a SQL server that was formatted and reconfigured. Prior to the
format, I was able to access this server from remote locations by creating an
ODBC connection in Administrative Tools in Windows XP. I haven't changed my
firewall or the server IP. As far as I can see, everything should be the
same. The problem now is that I can't create an ODBC connection unless I'm
on my network and a member of the domain. Even if I'm with my network, but
not a member of the domain, I can't create the ODBC connection.
The server is set up using mixed-mode authentication and as I mentioned, I
can create this connection if I'm on the domain. Any suggestions as to why I
can't do this remotely? Thanks in advance for your help.Hi
Can you see the server (using ping?). Which protocols do you have enabled?
Is the SQL Server on the domain? Have you re-created the users, logins and
trusts to be exactly the same? What error message do you get?
John
"J.B.C" <JBC@.discussions.microsoft.com> wrote in message
news:F9887DA2-34B9-42F2-A903-CBF04CE9DDD7@.microsoft.com...
>I have a SQL server that was formatted and reconfigured. Prior to the
> format, I was able to access this server from remote locations by creating
> an
> ODBC connection in Administrative Tools in Windows XP. I haven't changed
> my
> firewall or the server IP. As far as I can see, everything should be
> the
> same. The problem now is that I can't create an ODBC connection unless
> I'm
> on my network and a member of the domain. Even if I'm with my network,
> but
> not a member of the domain, I can't create the ODBC connection.
> The server is set up using mixed-mode authentication and as I mentioned, I
> can create this connection if I'm on the domain. Any suggestions as to
> why I
> can't do this remotely? Thanks in advance for your help.

Remote SQl connection

I have a SQL server that was formatted and reconfigured. Prior to the
format, I was able to access this server from remote locations by creating an
ODBC connection in Administrative Tools in Windows XP. I haven't changed my
firewall or the server IP. As far as I can see, everything should be the
same. The problem now is that I can't create an ODBC connection unless I'm
on my network and a member of the domain. Even if I'm with my network, but
not a member of the domain, I can't create the ODBC connection.
The server is set up using mixed-mode authentication and as I mentioned, I
can create this connection if I'm on the domain. Any suggestions as to why I
can't do this remotely? Thanks in advance for your help.
Hi
Can you see the server (using ping?). Which protocols do you have enabled?
Is the SQL Server on the domain? Have you re-created the users, logins and
trusts to be exactly the same? What error message do you get?
John
"J.B.C" <JBC@.discussions.microsoft.com> wrote in message
news:F9887DA2-34B9-42F2-A903-CBF04CE9DDD7@.microsoft.com...
>I have a SQL server that was formatted and reconfigured. Prior to the
> format, I was able to access this server from remote locations by creating
> an
> ODBC connection in Administrative Tools in Windows XP. I haven't changed
> my
> firewall or the server IP. As far as I can see, everything should be
> the
> same. The problem now is that I can't create an ODBC connection unless
> I'm
> on my network and a member of the domain. Even if I'm with my network,
> but
> not a member of the domain, I can't create the ODBC connection.
> The server is set up using mixed-mode authentication and as I mentioned, I
> can create this connection if I'm on the domain. Any suggestions as to
> why I
> can't do this remotely? Thanks in advance for your help.

Remote server

Here is a scenario what i want to do:
I have SQL 2000 server on windows 2000 server in two
different locations. I want to setup the local server to
copy the data to the remote server every 30 minutes or
so. In case the local server is down, i want to redirect
users to the other database server. Which way to go
either log shipping or replication? or any othere
suggestion? maybe third party tools.
Thank you.>--Original Message--
>Here is a scenario what i want to do:
>I have SQL 2000 server on windows 2000 server in two
>different locations. I want to setup the local server
to
>copy the data to the remote server every 30 minutes or
>so. In case the local server is down, i want to redirect
>users to the other database server. Which way to go
>either log shipping or replication? or any othere
>suggestion? maybe third party tools.
>Thank you.
1. You can use Double-Take for real-time replication and
failover reasons (when first server is down the
second "take" the ip address and is coming up).
2. Log shipping + scripts. Script must detect if first
server is down and change the ip address of the second
server
Cezar|||I'd be extremely careful with automatically switching the clients to the
warm standby server maintained via log shipping. Unless you carefully wire a
lot of automated and robust checks to ensure that all conditions are in
place as you have agreed with the business, it's too dangerous to let it
happen automatically.
I myself have never recommended or allowed any automatic switch to a warm
standby server. Nor have I heard anybody doing it in a serious production
environment. (I have a feeling that I might just hear from somebody here :-)
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"cezar" <cezar_gheorghe@.hotmail.com> wrote in message
news:0a6601c3817b$e0338860$a401280a@.phx.gbl...
> >--Original Message--
> >Here is a scenario what i want to do:
> >
> >I have SQL 2000 server on windows 2000 server in two
> >different locations. I want to setup the local server
> to
> >copy the data to the remote server every 30 minutes or
> >so. In case the local server is down, i want to redirect
> >users to the other database server. Which way to go
> >either log shipping or replication? or any othere
> >suggestion? maybe third party tools.
> >
> >Thank you.
> 1. You can use Double-Take for real-time replication and
> failover reasons (when first server is down the
> second "take" the ip address and is coming up).
> 2. Log shipping + scripts. Script must detect if first
> server is down and change the ip address of the second
> server
> Cezar