How to connect to remote server

Hi All,

I have created my sql database script using SQL data publishing wizard, now i want to execute the same on my shared hosting database. But i am not getting any option to connect to remote server in SSMSE.

I have developed web based application with back hand as SQL Server 2005, so now i want to execute my script file onto the server. so how i will connect with my server using SSMSE ?

My application is located under www.briskonsales.com/sales

Any idea ?

Thanks,

Jay

You will have to work with your Hosting provider to obtain access through their firewalls to access their SQL Server instance.

|||Is the remote instance a SQL Server Express edition ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

Very few hosting providers will allow you to connect to their server using SSMS; rather they provide their own set of management tools accessable through their site. If you log into your account you will likely find a set of links that take you to the management console for your hosted database. From there you should be able to load the script file that you saved from the DPW and run it to create your objects in the hosted database.

As others mention, contact your hosting provider if you have questions about managing your hosted database.

Mike

How to connect on shared memory?

I finally installed service pack 3, and I am told that I Can still access SQL server locally thru shared memory interfaces, if I turn off the Named Pipes and TCP/IP network libraries, thereby stopping UDP port 1434 from listening. This does, indeed stop port 1434 from listening but I can't use Enterprise manager to connect to the server anymore. How to I get it to connect on shared memory?Shared memory only works from the SQL Server itself. Not terribly useful for a networked application, but there it is. If you are trying to connect from a client machine, you will nee to turn on either TCP/IP or Named Pipes. Then make sure that the client machine is using the same protocol.

If you are attempting to access the SQL Server locally, you can use the Client Network Utility (in start menu) to reset your default protocol to Shared Memory (or TCP/IP, Named Pipes, etc.)

Hope this helps.|||Indeed it did. I found this out myself last night. Of course, remote clients can't connect. But, the purpose of this server is not for remote clients. I'm using it for IIS to connect to, so I can write ASP.Net scripts. There's a checkbox in the Client Network Utility titled "Enable Shared Memory Protocol" that allows you to do this, for future reference if anyone else has this problem.

How to configure MSDE to listen on TCP/IP

Hi:
I'm not able to connect to MSDE remotely. From the SQL Server logs, it
is listening on Shared Memory only. How do I configure it to listen on
TCP/IP ?
The MSDE is running on WinXP Pro SP2, and there is a instance of
SQL2005 Express installed side by side, the SQL2005 Express is
configure to listen on port 1618. The firewall already turned off.
Another problem is related to SQL2005 Express... I'm not able to
connect to the SQL2005 Express remotely when the firewall turned ON,
even port 1618 is already add into exception list.
Any idea ?
Thanks
JCVoon
Problem solved. I enable the Named Pipes protocol using SVRNETCN.exe
and restart the MSDE.
Why must enabled the Named Pipes when I only need TCP/IP protocol ?
JCVoon
On Jan 25, 12:45 pm, "jcvoon" <jiangchnan.v...@.maximas.com> wrote:
> Hi:
> I'm not able to connect to MSDE remotely. From the SQL Server logs, it
> is listening on Shared Memory only. How do I configure it to listen on
> TCP/IP ?
> The MSDE is running on WinXP Pro SP2, and there is a instance of
> SQL2005 Express installed side by side, the SQL2005 Express is
> configure to listen on port 1618. The firewall already turned off.
> Another problem is related to SQL2005 Express... I'm not able to
> connect to the SQL2005 Express remotely when the firewall turned ON,
> even port 1618 is already add into exception list.
> Any idea ?
> Thanks
> JCVoon
|||network communications are typically more interactive for named pipes whereas.
data transmissions are more streamlined and have less overhead in TCP/IP
You can have more in SQL BOL
"jcvoon" wrote:

> Problem solved. I enable the Named Pipes protocol using SVRNETCN.exe
> and restart the MSDE.
> Why must enabled the Named Pipes when I only need TCP/IP protocol ?
> JCVoon
>
> On Jan 25, 12:45 pm, "jcvoon" <jiangchnan.v...@.maximas.com> wrote:
>
|||> Another problem is related to SQL2005 Express... I'm not able to
> connect to the SQL2005 Express remotely when the firewall turned ON,
> even port 1618 is already add into exception list.
You have to add the C:\Program Files\Microsoft SQL
Server\90\Shared\sqlbrowser.exe into the exceptions list.

How to configure MSDE to listen on TCP/IP

Hi:
I'm not able to connect to MSDE remotely. From the SQL Server logs, it
is listening on Shared Memory only. How do I configure it to listen on
TCP/IP ?
The MSDE is running on WinXP Pro SP2, and there is a instance of
SQL2005 Express installed side by side, the SQL2005 Express is
configure to listen on port 1618. The firewall already turned off.
Another problem is related to SQL2005 Express... I'm not able to
connect to the SQL2005 Express remotely when the firewall turned ON,
even port 1618 is already add into exception list.
Any idea ?
Thanks
JCVoonProblem solved. I enable the Named Pipes protocol using SVRNETCN.exe
and restart the MSDE.
Why must enabled the Named Pipes when I only need TCP/IP protocol '
JCVoon
On Jan 25, 12:45 pm, "jcvoon" <jiangchnan.v...@.maximas.com> wrote:
> Hi:
> I'm not able to connect to MSDE remotely. From the SQL Server logs, it
> is listening on Shared Memory only. How do I configure it to listen on
> TCP/IP ?
> The MSDE is running on WinXP Pro SP2, and there is a instance of
> SQL2005 Express installed side by side, the SQL2005 Express is
> configure to listen on port 1618. The firewall already turned off.
> Another problem is related to SQL2005 Express... I'm not able to
> connect to the SQL2005 Express remotely when the firewall turned ON,
> even port 1618 is already add into exception list.
> Any idea ?
> Thanks
> JCVoon|||network communications are typically more interactive for named pipes wherea
s.
data transmissions are more streamlined and have less overhead in TCP/IP
You can have more in SQL BOL
"jcvoon" wrote:

> Problem solved. I enable the Named Pipes protocol using SVRNETCN.exe
> and restart the MSDE.
> Why must enabled the Named Pipes when I only need TCP/IP protocol '
> JCVoon
>
> On Jan 25, 12:45 pm, "jcvoon" <jiangchnan.v...@.maximas.com> wrote:
>|||> Another problem is related to SQL2005 Express... I'm not able to
> connect to the SQL2005 Express remotely when the firewall turned ON,
> even port 1618 is already add into exception list.
You have to add the C:\Program Files\Microsoft SQL
Server\90\Shared\sqlbrowser.exe into the exceptions list.

How to configure MSDE to listen on TCP/IP

Hi:
I'm not able to connect to MSDE remotely. From the SQL Server logs, it
is listening on Shared Memory only. How do I configure it to listen on
TCP/IP ?
The MSDE is running on WinXP Pro SP2, and there is a instance of
SQL2005 Express installed side by side, the SQL2005 Express is
configure to listen on port 1618. The firewall already turned off.
Another problem is related to SQL2005 Express... I'm not able to
connect to the SQL2005 Express remotely when the firewall turned ON,
even port 1618 is already add into exception list.
Any idea ?
Thanks
JCVoonProblem solved. I enable the Named Pipes protocol using SVRNETCN.exe
and restart the MSDE.
Why must enabled the Named Pipes when I only need TCP/IP protocol '
JCVoon
On Jan 25, 12:45 pm, "jcvoon" <jiangchnan.v...@.maximas.com> wrote:
> Hi:
> I'm not able to connect to MSDE remotely. From the SQL Server logs, it
> is listening on Shared Memory only. How do I configure it to listen on
> TCP/IP ?
> The MSDE is running on WinXP Pro SP2, and there is a instance of
> SQL2005 Express installed side by side, the SQL2005 Express is
> configure to listen on port 1618. The firewall already turned off.
> Another problem is related to SQL2005 Express... I'm not able to
> connect to the SQL2005 Express remotely when the firewall turned ON,
> even port 1618 is already add into exception list.
> Any idea ?
> Thanks
> JCVoon|||network communications are typically more interactive for named pipes whereas.
data transmissions are more streamlined and have less overhead in TCP/IP
You can have more in SQL BOL
"jcvoon" wrote:
> Problem solved. I enable the Named Pipes protocol using SVRNETCN.exe
> and restart the MSDE.
> Why must enabled the Named Pipes when I only need TCP/IP protocol '
> JCVoon
>
> On Jan 25, 12:45 pm, "jcvoon" <jiangchnan.v...@.maximas.com> wrote:
> > Hi:
> >
> > I'm not able to connect to MSDE remotely. From the SQL Server logs, it
> > is listening on Shared Memory only. How do I configure it to listen on
> > TCP/IP ?
> >
> > The MSDE is running on WinXP Pro SP2, and there is a instance of
> > SQL2005 Express installed side by side, the SQL2005 Express is
> > configure to listen on port 1618. The firewall already turned off.
> >
> > Another problem is related to SQL2005 Express... I'm not able to
> > connect to the SQL2005 Express remotely when the firewall turned ON,
> > even port 1618 is already add into exception list.
> >
> > Any idea ?
> >
> > Thanks
> > JCVoon
>|||> Another problem is related to SQL2005 Express... I'm not able to
> connect to the SQL2005 Express remotely when the firewall turned ON,
> even port 1618 is already add into exception list.
You have to add the C:\Program Files\Microsoft SQL
Server\90\Shared\sqlbrowser.exe into the exceptions list.