Hi,
is it possible to manage a Remote Sql2000 trough a local installed Entrepise
manager 7.0 ?
GL.No, only the ther way.
HTH, Jens Suessmeyer.|||No, EM 7 cannot connect to SQL Server 2000.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Grard Leclercq" <gl@.pasdemail.fr> wrote in message
news:DiEIf.258469$3P4.7890037@.phobos.telenet-ops.be...
> Hi,
> is it possible to manage a Remote Sql2000 trough a local installed Entrepi
se manager 7.0 ?
> GL.
>
Showing posts with label manage. Show all posts
Showing posts with label manage. Show all posts
Wednesday, March 21, 2012
Friday, March 9, 2012
Remote management of database
trying to connect to remote MSDE database to manage it
--msde instance with DISABLENETWORKPROTOCOLS=0 is installed and working.
--local connection works to confirm username and password
--firewall ports are configured correctly and listening
--remote telnet connection works to confirm ip and port #
--ASP page can connect and return results from query
but tcp/ip does not connect
any suggestions on how to fix/make a tcp/ip connection work ?TJS wrote:
> trying to connect to remote MSDE database to manage it
> --msde instance with DISABLENETWORKPROTOCOLS=0 is installed and working.
> --local connection works to confirm username and password
> --firewall ports are configured correctly and listening
> --remote telnet connection works to confirm ip and port #
> --ASP page can connect and return results from query
> but tcp/ip does not connect
> any suggestions on how to fix/make a tcp/ip connection work ?
>
Well, MSDE (which is a free desktop editiion) normally doesn't work for outs
ide connections(they
don't want you to use the free version as a real server :)),
but i remember that some time ago on a web site i've seen a trick to make it
work. Try googling.|||I searched for a solution before coming here.
"MuZZy" <leyandrew@.yahoo.com> wrote in message
news:A7adnSWJuc_pCKbfRVn-vg@.comcast.com...
> TJS wrote:
> Well, MSDE (which is a free desktop editiion) normally doesn't work for
> outside connections(they don't want you to use the free version as a real
> server :)),
> but i remember that some time ago on a web site i've seen a trick to make
> it work. Try googling.
--msde instance with DISABLENETWORKPROTOCOLS=0 is installed and working.
--local connection works to confirm username and password
--firewall ports are configured correctly and listening
--remote telnet connection works to confirm ip and port #
--ASP page can connect and return results from query
but tcp/ip does not connect
any suggestions on how to fix/make a tcp/ip connection work ?TJS wrote:
> trying to connect to remote MSDE database to manage it
> --msde instance with DISABLENETWORKPROTOCOLS=0 is installed and working.
> --local connection works to confirm username and password
> --firewall ports are configured correctly and listening
> --remote telnet connection works to confirm ip and port #
> --ASP page can connect and return results from query
> but tcp/ip does not connect
> any suggestions on how to fix/make a tcp/ip connection work ?
>
Well, MSDE (which is a free desktop editiion) normally doesn't work for outs
ide connections(they
don't want you to use the free version as a real server :)),
but i remember that some time ago on a web site i've seen a trick to make it
work. Try googling.|||I searched for a solution before coming here.
"MuZZy" <leyandrew@.yahoo.com> wrote in message
news:A7adnSWJuc_pCKbfRVn-vg@.comcast.com...
> TJS wrote:
> Well, MSDE (which is a free desktop editiion) normally doesn't work for
> outside connections(they don't want you to use the free version as a real
> server :)),
> but i remember that some time ago on a web site i've seen a trick to make
> it work. Try googling.
Remote Manage SQL Server Agent via SSMS
When I open up SSMS from the SQL Server 2005 box itself I can see all SQL
Server Agent jobs. When I open a specific job I can see the owner and steps
etc. When I use SSMS remotely from my Vista laptop to connect to the SQL
Server 2005 instance I can see the jobs, but when I go to look at properties
it is acting like it is a new job with none of the actual owner/config
information. The account I am using to connect in both cases is the same
account and is in the sysadmin role. Any advice is appreciated.
Thanks
--
Adam SYou need to install SP2 or later on your client machine. I believe you have
a mismatch between client and server (a later edition has probably been
upgraded on the server). You should always try to maintain consistency
between the version of tools installed on the server and all clients that
will access it...
A
"Adam S" <Adam S@.community.nospam> wrote in message
news:7B3CEA63-4090-48D4-AFEA-70487F537E5E@.microsoft.com...
> When I open up SSMS from the SQL Server 2005 box itself I can see all SQL
> Server Agent jobs. When I open a specific job I can see the owner and
> steps
> etc. When I use SSMS remotely from my Vista laptop to connect to the SQL
> Server 2005 instance I can see the jobs, but when I go to look at
> properties
> it is acting like it is a new job with none of the actual owner/config
> information. The account I am using to connect in both cases is the same
> account and is in the sysadmin role. Any advice is appreciated.
> Thanks
> --
> Adam S
Server Agent jobs. When I open a specific job I can see the owner and steps
etc. When I use SSMS remotely from my Vista laptop to connect to the SQL
Server 2005 instance I can see the jobs, but when I go to look at properties
it is acting like it is a new job with none of the actual owner/config
information. The account I am using to connect in both cases is the same
account and is in the sysadmin role. Any advice is appreciated.
Thanks
--
Adam SYou need to install SP2 or later on your client machine. I believe you have
a mismatch between client and server (a later edition has probably been
upgraded on the server). You should always try to maintain consistency
between the version of tools installed on the server and all clients that
will access it...
A
"Adam S" <Adam S@.community.nospam> wrote in message
news:7B3CEA63-4090-48D4-AFEA-70487F537E5E@.microsoft.com...
> When I open up SSMS from the SQL Server 2005 box itself I can see all SQL
> Server Agent jobs. When I open a specific job I can see the owner and
> steps
> etc. When I use SSMS remotely from my Vista laptop to connect to the SQL
> Server 2005 instance I can see the jobs, but when I go to look at
> properties
> it is acting like it is a new job with none of the actual owner/config
> information. The account I am using to connect in both cases is the same
> account and is in the sysadmin role. Any advice is appreciated.
> Thanks
> --
> Adam S
Remote Manage SQL Server Agent via SSMS
When I open up SSMS from the SQL Server 2005 box itself I can see all SQL
Server Agent jobs. When I open a specific job I can see the owner and steps
etc. When I use SSMS remotely from my Vista laptop to connect to the SQL
Server 2005 instance I can see the jobs, but when I go to look at properties
it is acting like it is a new job with none of the actual owner/config
information. The account I am using to connect in both cases is the same
account and is in the sysadmin role. Any advice is appreciated.
Thanks
Adam SYou need to install SP2 or later on your client machine. I believe you have
a mismatch between client and server (a later edition has probably been
upgraded on the server). You should always try to maintain consistency
between the version of tools installed on the server and all clients that
will access it...
A
"Adam S" <Adam S@.community.nospam> wrote in message
news:7B3CEA63-4090-48D4-AFEA-70487F537E5E@.microsoft.com...
> When I open up SSMS from the SQL Server 2005 box itself I can see all SQL
> Server Agent jobs. When I open a specific job I can see the owner and
> steps
> etc. When I use SSMS remotely from my Vista laptop to connect to the SQL
> Server 2005 instance I can see the jobs, but when I go to look at
> properties
> it is acting like it is a new job with none of the actual owner/config
> information. The account I am using to connect in both cases is the same
> account and is in the sysadmin role. Any advice is appreciated.
> Thanks
> --
> Adam S
Server Agent jobs. When I open a specific job I can see the owner and steps
etc. When I use SSMS remotely from my Vista laptop to connect to the SQL
Server 2005 instance I can see the jobs, but when I go to look at properties
it is acting like it is a new job with none of the actual owner/config
information. The account I am using to connect in both cases is the same
account and is in the sysadmin role. Any advice is appreciated.
Thanks
Adam SYou need to install SP2 or later on your client machine. I believe you have
a mismatch between client and server (a later edition has probably been
upgraded on the server). You should always try to maintain consistency
between the version of tools installed on the server and all clients that
will access it...
A
"Adam S" <Adam S@.community.nospam> wrote in message
news:7B3CEA63-4090-48D4-AFEA-70487F537E5E@.microsoft.com...
> When I open up SSMS from the SQL Server 2005 box itself I can see all SQL
> Server Agent jobs. When I open a specific job I can see the owner and
> steps
> etc. When I use SSMS remotely from my Vista laptop to connect to the SQL
> Server 2005 instance I can see the jobs, but when I go to look at
> properties
> it is acting like it is a new job with none of the actual owner/config
> information. The account I am using to connect in both cases is the same
> account and is in the sysadmin role. Any advice is appreciated.
> Thanks
> --
> Adam S
Remote Manage SQL Server Agent via SSMS
When I open up SSMS from the SQL Server 2005 box itself I can see all SQL
Server Agent jobs. When I open a specific job I can see the owner and steps
etc. When I use SSMS remotely from my Vista laptop to connect to the SQL
Server 2005 instance I can see the jobs, but when I go to look at properties
it is acting like it is a new job with none of the actual owner/config
information. The account I am using to connect in both cases is the same
account and is in the sysadmin role. Any advice is appreciated.
Thanks
Adam S
You need to install SP2 or later on your client machine. I believe you have
a mismatch between client and server (a later edition has probably been
upgraded on the server). You should always try to maintain consistency
between the version of tools installed on the server and all clients that
will access it...
A
"Adam S" <Adam S@.community.nospam> wrote in message
news:7B3CEA63-4090-48D4-AFEA-70487F537E5E@.microsoft.com...
> When I open up SSMS from the SQL Server 2005 box itself I can see all SQL
> Server Agent jobs. When I open a specific job I can see the owner and
> steps
> etc. When I use SSMS remotely from my Vista laptop to connect to the SQL
> Server 2005 instance I can see the jobs, but when I go to look at
> properties
> it is acting like it is a new job with none of the actual owner/config
> information. The account I am using to connect in both cases is the same
> account and is in the sysadmin role. Any advice is appreciated.
> Thanks
> --
> Adam S
Server Agent jobs. When I open a specific job I can see the owner and steps
etc. When I use SSMS remotely from my Vista laptop to connect to the SQL
Server 2005 instance I can see the jobs, but when I go to look at properties
it is acting like it is a new job with none of the actual owner/config
information. The account I am using to connect in both cases is the same
account and is in the sysadmin role. Any advice is appreciated.
Thanks
Adam S
You need to install SP2 or later on your client machine. I believe you have
a mismatch between client and server (a later edition has probably been
upgraded on the server). You should always try to maintain consistency
between the version of tools installed on the server and all clients that
will access it...
A
"Adam S" <Adam S@.community.nospam> wrote in message
news:7B3CEA63-4090-48D4-AFEA-70487F537E5E@.microsoft.com...
> When I open up SSMS from the SQL Server 2005 box itself I can see all SQL
> Server Agent jobs. When I open a specific job I can see the owner and
> steps
> etc. When I use SSMS remotely from my Vista laptop to connect to the SQL
> Server 2005 instance I can see the jobs, but when I go to look at
> properties
> it is acting like it is a new job with none of the actual owner/config
> information. The account I am using to connect in both cases is the same
> account and is in the sysadmin role. Any advice is appreciated.
> Thanks
> --
> Adam S
Remote Manage
Before I just manage the SQL serve in LAN.
Right now i have a SQL server on internet I want to Remote manage
Can I still use QA and Enterprise Manager ?Yes, you can use Query Analyzer and SQL Enterprise Manager to manage a server that is open to the Internet. I would consider making an exception at your firewall to allow that server to remain part of your NT domain, so that you can use NT Authentication instead of SQL Authentication.
-PatP|||how can I set some config on my Enterprise manager or QA?|||Huh? I don't understand what you are asking.
-PatP|||Sorry about confuse,
I dont have this kind of experience. Before i just install client software like
QA or Enterprise in my PC ,i can use this software manage my SQL Server on LAN.
Right now another SQL server on WAN ,i dont know can i use QA to find
SQL server or I have to get some remote software to log on remote server
and use remote server's QA?
Do i make me clearly?|||Now I understand the question better!
When you are making the connection to the server in Query Analyzer, type either the server's name or IP address into the box labled SQL Server. Except for the lack of ability to enumerate remote servers (having Query Analyzer locate the SQL Servers and provide a list of them for you), the connection process is exactly the same as a "local" SQL Server.
-PatP
Right now i have a SQL server on internet I want to Remote manage
Can I still use QA and Enterprise Manager ?Yes, you can use Query Analyzer and SQL Enterprise Manager to manage a server that is open to the Internet. I would consider making an exception at your firewall to allow that server to remain part of your NT domain, so that you can use NT Authentication instead of SQL Authentication.
-PatP|||how can I set some config on my Enterprise manager or QA?|||Huh? I don't understand what you are asking.
-PatP|||Sorry about confuse,
I dont have this kind of experience. Before i just install client software like
QA or Enterprise in my PC ,i can use this software manage my SQL Server on LAN.
Right now another SQL server on WAN ,i dont know can i use QA to find
SQL server or I have to get some remote software to log on remote server
and use remote server's QA?
Do i make me clearly?|||Now I understand the question better!
When you are making the connection to the server in Query Analyzer, type either the server's name or IP address into the box labled SQL Server. Except for the lack of ability to enumerate remote servers (having Query Analyzer locate the SQL Servers and provide a list of them for you), the connection process is exactly the same as a "local" SQL Server.
-PatP
Subscribe to:
Posts (Atom)