asp sql server: remote

Showing posts with label remote. Show all posts

Tuesday, March 27, 2012

connection problem

Hi, All,
SQL7.0, SP3 on Win2000 server+ sp1
I remote access our client in FL, recently I get error
message [DBNMPNTW] Connection write(writefile()) message
then the connection failed.
What's cause the problem how can I fix it.
Thanks and have a nice day
HawkHi Hawk,
Connection write using the Named Pipes library. There could be a
permission problem with Named Pipes /SMB or a restrictive Security Template
setting. Try connecting using TCP.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
Thanks, but how can change it to TCP? Could you tell me
more?
Have a good weekend

>--Original Message--
>Hi Hawk,
> Connection write using the Named Pipes library.
There could be a
>permission problem with Named Pipes /SMB or a
restrictive Security Template
>setting. Try connecting using TCP.
>
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>|||Use the SQL Client Network Utility and create a TCP alias. Enter the
actual servername for the alias, this way the client will use sockets
instead.
If you have MDAC 2.6 on the client you can also try this as a test.
osql -Stcp:ServerNameHere -UuserName -Ppassword
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thank you very much and have a good one
Hawk

connection problem

Hi.
I have installed Microsoft SQL Server Desktop on Windows XP Pro. I can
connect to database from remote machines with Windows 98Se, but i can't
connect from machines with Windows XP.
ChrisI think that it is a problem with not having the 'correct' client network
utilities installed.
On the Start menu, select [All Programs], [Microsoft SQL Server], th
en
[Client Network Utility].
In the [Enabled Protocols] window, you should have both TCP/IP and Named
Pipes.
If one is missing, select the missing protocol from the list on the left
side, and click the [Enable] button.
Hopefully, if my memory is correct, that will take care of the problem.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Krzysztof" <colinkj@.poczta.onet.pl> wrote in message
news:eb0a61$jov$1@.nemesis.news.tpi.pl...
> Hi.
> I have installed Microsoft SQL Server Desktop on Windows XP Pro. I can
> connect to database from remote machines with Windows 98Se, but i can't
> connect from machines with Windows XP.
> Chris
>
>|||Have you tried temporarily disabling the firewall on the XP machines?
John Opincar
john.opincar@.sundesksoftware.com
"Krzysztof" <colinkj@.poczta.onet.pl> wrote in message
news:eb0a61$jov$1@.nemesis.news.tpi.pl...
> Hi.
> I have installed Microsoft SQL Server Desktop on Windows XP Pro. I can
> connect to database from remote machines with Windows 98Se, but i can't
> connect from machines with Windows XP.
> Chris
>
>

Sunday, March 25, 2012

connection problem

Hi, All,
SQL7.0, SP3 on Win2000 server+ sp1
I remote access our client in FL, recently I get error
message [DBNMPNTW] Connection write(writefile()) message
then the connection failed.
What's cause the problem how can I fix it.
Thanks and have a nice day
Hawk
Hi Hawk,
Connection write using the Named Pipes library. There could be a
permission problem with Named Pipes /SMB or a restrictive Security Template
setting. Try connecting using TCP.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Kevin,
Thanks, but how can change it to TCP? Could you tell me
more?
Have a good weekend

>--Original Message--
>Hi Hawk,
> Connection write using the Named Pipes library.
There could be a
>permission problem with Named Pipes /SMB or a
restrictive Security Template
>setting. Try connecting using TCP.
>
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>
|||Use the SQL Client Network Utility and create a TCP alias. Enter the
actual servername for the alias, this way the client will use sockets
instead.
If you have MDAC 2.6 on the client you can also try this as a test.
osql -Stcp:ServerNameHere -UuserName -Ppassword
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Thank you very much and have a good one
Hawk

Thursday, March 22, 2012

Connection over Internet

Is it possible to connect EM to a remote server that is not on a LAN or WAN?
Thanks.
Hi
You would need to start EM on the machine itself if there are no network
connections.
John
"Vik" wrote:

> Is it possible to connect EM to a remote server that is not on a LAN or WAN?
> Thanks.
>
>
|||Hi
The previous reply assumed that there isn't a VPN connection! If there is
then you should be able to connect it if the ports correct ports are open on
the firewall. http://support.microsoft.com/kb/287932
You could also try using the web administrator
http://www.microsoft.com/downloads/details.aspx?FamilyID=c039a798-c57a-419e-acbc-2a332cb7f959&displaylang=en
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:14E75EEC-6134-43BF-AE4D-56C4D74E28BF@.microsoft.com...[vbcol=seagreen]
> Hi
> You would need to start EM on the machine itself if there are no network
> connections.
> John
> "Vik" wrote:
sql sql

Connection over Internet

Is it possible to connect EM to a remote server that is not on a LAN or WAN?
Thanks.Hi
You would need to start EM on the machine itself if there are no network
connections.
John
"Vik" wrote:
> Is it possible to connect EM to a remote server that is not on a LAN or WAN?
> Thanks.
>
>|||Hi
The previous reply assumed that there isn't a VPN connection! If there is
then you should be able to connect it if the ports correct ports are open on
the firewall. http://support.microsoft.com/kb/287932
You could also try using the web administrator
http://www.microsoft.com/downloads/details.aspx?FamilyID=c039a798-c57a-419e-acbc-2a332cb7f959&displaylang=en
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:14E75EEC-6134-43BF-AE4D-56C4D74E28BF@.microsoft.com...
> Hi
> You would need to start EM on the machine itself if there are no network
> connections.
> John
> "Vik" wrote:
>> Is it possible to connect EM to a remote server that is not on a LAN or
>> WAN?
>> Thanks.
>>

Sunday, March 11, 2012

Connection from PHP slower when server is remote

I'm trying to get some clues on why I get (much) slower responses from
my PHP applications when dealing with a remote sql server as opposed to
a local sql server.
Here's my situation:
Server #1
MSSQL 2000 sp4
Windows 2000 Server
PHP4 on IIS5 (CGI)
Server #2
MSSQL 2000 sp4
Windows 2003 Server
PHP4 on IIS6 (CGI)
Server #1 and #2 are on the same local network and the same switch. We
use TCP/IP as the connection protocol and our connections use IPs
instead of domain names.
Server#1PHP --> Server#2 MSSQL = slow
Server#2PHP --> Server#1 MSSQL = slow
Server#1PHP --> Server#1 MSSQL = fast
Server#2PHP --> Server#2 MSSQL = fast
This slower behavior is most noticable when many stored procedures
(10-15) are being executed on one php page. When the database is local
on a page such as this, the response time is around 2 seconds. When the
sql server is remote, the response time is between 8 and 15 seconds.
Does this make sense at all? Does anyone have any ideas of what the
bottleneck could be?
Hi
You may want to look at how your network is performing using an network
monitoring tool and perfmon. A local SQL Server could be using shared memory
which may be more significant on a poorly performing network.
You can also use SQL profiler to compare the times taken to execute the
stored procedures on each of the servers, this will allow you to check if
they are similar or acceptable if they are on different hardware.
Check that indexes are not fragmented and statistics are up to date on each
machine. Make sure that you have either a maintenance plan or some job that
will run periodically to maintain your indexes and statistics.
You may also what to check fragmentation of the physical disc. If you HDD is
very fragmented you may want to stop SQL Server and defrag it.
John
"gharmel" wrote:

> I'm trying to get some clues on why I get (much) slower responses from
> my PHP applications when dealing with a remote sql server as opposed to
> a local sql server.
> Here's my situation:
> Server #1
> MSSQL 2000 sp4
> Windows 2000 Server
> PHP4 on IIS5 (CGI)
> Server #2
> MSSQL 2000 sp4
> Windows 2003 Server
> PHP4 on IIS6 (CGI)
> Server #1 and #2 are on the same local network and the same switch. We
> use TCP/IP as the connection protocol and our connections use IPs
> instead of domain names.
> Server#1PHP --> Server#2 MSSQL = slow
> Server#2PHP --> Server#1 MSSQL = slow
> Server#1PHP --> Server#1 MSSQL = fast
> Server#2PHP --> Server#2 MSSQL = fast
> This slower behavior is most noticable when many stored procedures
> (10-15) are being executed on one php page. When the database is local
> on a page such as this, the response time is around 2 seconds. When the
> sql server is remote, the response time is between 8 and 15 seconds.
> Does this make sense at all? Does anyone have any ideas of what the
> bottleneck could be?
>
|||After more investigation it seems that every query had a connect and
disconnect. The act of connecting/disconnecting seems to be much more
expensive when the SQL server is not local.
|||Hi
Usually connection pooling is used to overcome this.
John
"gharmel" wrote:

> After more investigation it seems that every query had a connect and
> disconnect. The act of connecting/disconnecting seems to be much more
> expensive when the SQL server is not local.
>

Connection from PHP slower when server is remote

I'm trying to get some clues on why I get (much) slower responses from
my php applications when dealing with a remote sql server as opposed to
a local sql server.
Here's my situation:
Server #1
MSSQL 2000 sp4
Windows 2000 Server
PHP4 on IIS5 (CGI)
Server #2
MSSQL 2000 sp4
Windows 2003 Server
PHP4 on IIS6 (CGI)
Server #1 and #2 are on the same local network and the same switch. We
use TCP/IP as the connection protocol and our connections use IPs
instead of domain names.
Server#1PHP --> Server#2 MSSQL = slow
Server#2PHP --> Server#1 MSSQL = slow
Server#1PHP --> Server#1 MSSQL = fast
Server#2PHP --> Server#2 MSSQL = fast
This slower behavior is most noticable when many stored procedures
(10-15) are being executed on one php page. When the database is local
on a page such as this, the response time is around 2 seconds. When the
sql server is remote, the response time is between 8 and 15 seconds.
Does this make sense at all? Does anyone have any ideas of what the
bottleneck could be?Hi
You may want to look at how your network is performing using an network
monitoring tool and perfmon. A local SQL Server could be using shared memory
which may be more significant on a poorly performing network.
You can also use SQL profiler to compare the times taken to execute the
stored procedures on each of the servers, this will allow you to check if
they are similar or acceptable if they are on different hardware.
Check that indexes are not fragmented and statistics are up to date on each
machine. Make sure that you have either a maintenance plan or some job that
will run periodically to maintain your indexes and statistics.
You may also what to check fragmentation of the physical disc. If you HDD is
very fragmented you may want to stop SQL Server and defrag it.
John
"gharmel" wrote:

> I'm trying to get some clues on why I get (much) slower responses from
> my php applications when dealing with a remote sql server as opposed to
> a local sql server.
> Here's my situation:
> Server #1
> MSSQL 2000 sp4
> Windows 2000 Server
> PHP4 on IIS5 (CGI)
> Server #2
> MSSQL 2000 sp4
> Windows 2003 Server
> PHP4 on IIS6 (CGI)
> Server #1 and #2 are on the same local network and the same switch. We
> use TCP/IP as the connection protocol and our connections use IPs
> instead of domain names.
> Server#1PHP --> Server#2 MSSQL = slow
> Server#2PHP --> Server#1 MSSQL = slow
> Server#1PHP --> Server#1 MSSQL = fast
> Server#2PHP --> Server#2 MSSQL = fast
> This slower behavior is most noticable when many stored procedures
> (10-15) are being executed on one php page. When the database is local
> on a page such as this, the response time is around 2 seconds. When the
> sql server is remote, the response time is between 8 and 15 seconds.
> Does this make sense at all? Does anyone have any ideas of what the
> bottleneck could be?
>|||After more investigation it seems that every query had a connect and
disconnect. The act of connecting/disconnecting seems to be much more
expensive when the SQL server is not local.|||Hi
Usually connection pooling is used to overcome this.
John
"gharmel" wrote:

> After more investigation it seems that every query had a connect and
> disconnect. The act of connecting/disconnecting seems to be much more
> expensive when the SQL server is not local.
>

Connection from PHP slower when server is remote

I'm trying to get some clues on why I get (much) slower responses from
my PHP applications when dealing with a remote sql server as opposed to
a local sql server.
Here's my situation:
Server #1
MSSQL 2000 sp4
Windows 2000 Server
PHP4 on IIS5 (CGI)
Server #2
MSSQL 2000 sp4
Windows 2003 Server
PHP4 on IIS6 (CGI)
Server #1 and #2 are on the same local network and the same switch. We
use TCP/IP as the connection protocol and our connections use IPs
instead of domain names.
Server#1PHP --> Server#2 MSSQL = slow
Server#2PHP --> Server#1 MSSQL = slow
Server#1PHP --> Server#1 MSSQL = fast
Server#2PHP --> Server#2 MSSQL = fast
This slower behavior is most noticable when many stored procedures
(10-15) are being executed on one php page. When the database is local
on a page such as this, the response time is around 2 seconds. When the
sql server is remote, the response time is between 8 and 15 seconds.
Does this make sense at all? Does anyone have any ideas of what the
bottleneck could be?Hi
You may want to look at how your network is performing using an network
monitoring tool and perfmon. A local SQL Server could be using shared memory
which may be more significant on a poorly performing network.
You can also use SQL profiler to compare the times taken to execute the
stored procedures on each of the servers, this will allow you to check if
they are similar or acceptable if they are on different hardware.
Check that indexes are not fragmented and statistics are up to date on each
machine. Make sure that you have either a maintenance plan or some job that
will run periodically to maintain your indexes and statistics.
You may also what to check fragmentation of the physical disc. If you HDD is
very fragmented you may want to stop SQL Server and defrag it.
John
"gharmel" wrote:
> I'm trying to get some clues on why I get (much) slower responses from
> my PHP applications when dealing with a remote sql server as opposed to
> a local sql server.
> Here's my situation:
> Server #1
> MSSQL 2000 sp4
> Windows 2000 Server
> PHP4 on IIS5 (CGI)
> Server #2
> MSSQL 2000 sp4
> Windows 2003 Server
> PHP4 on IIS6 (CGI)
> Server #1 and #2 are on the same local network and the same switch. We
> use TCP/IP as the connection protocol and our connections use IPs
> instead of domain names.
> Server#1PHP --> Server#2 MSSQL = slow
> Server#2PHP --> Server#1 MSSQL = slow
> Server#1PHP --> Server#1 MSSQL = fast
> Server#2PHP --> Server#2 MSSQL = fast
> This slower behavior is most noticable when many stored procedures
> (10-15) are being executed on one php page. When the database is local
> on a page such as this, the response time is around 2 seconds. When the
> sql server is remote, the response time is between 8 and 15 seconds.
> Does this make sense at all? Does anyone have any ideas of what the
> bottleneck could be?
>|||After more investigation it seems that every query had a connect and
disconnect. The act of connecting/disconnecting seems to be much more
expensive when the SQL server is not local.|||Hi
Usually connection pooling is used to overcome this.
John
"gharmel" wrote:
> After more investigation it seems that every query had a connect and
> disconnect. The act of connecting/disconnecting seems to be much more
> expensive when the SQL server is not local.
>

Thursday, March 8, 2012

connection failed - ODBC from remote SQL SERVER

hello,
im trying to create an ODBC data source from a SQL SERVER 2005 database located in a remoted pc.
Client---->PC1 : win 2000 sp4, not sql server
Remote server-->PC2 : win 2000 sp4, sql server 2005 express

From the Command Prompt, im typing "ping PC2" successfully.
After, in the ODBC datasource administrator-->System DNS tab, i choose "sql server" as a new data source , and in the server box , i'm typing PC2/SQLEXPRESS.

In the next steps, im typing the user-passwords.
The error :
connection failed
...
[microsoft][odbc sql server driver][named pipes]ConnectionOpen(CreateFile()).
Connection failed:
SQLState: '08001'
..
Client unable to establish connection

What goes wrong?
I follow the same steps locally, and everything is OK.

Sorry for my bad english:cool:Here's an article (http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx) on troubleshooting connectivity issues on SQL Server Express.|||SQL 2005 does not support the Named Pipes protocol by default. I would choose a different protocol, preferably TCP/IP. You can set the protocol using the Client Configuration button on the second screen of the DSN definition in the ODBC DSN applet.

-PatP

connection failed

When i try to connect from remote computer to sequel
server i get the followin message
connection failed.
i'm connecting using odbc, i'm new to this so all help
thanks in advance.
HI,
Create you create a Alias name for your sql server remote machine using the
"Client Network Utility" by providing
Protocol as TCP/IP, IP address of sql server machine and port number.
After this use this Alias name to connect to sql server machine.
Thanks
Hari
MCDBA
"mike" <anonymous@.discussions.microsoft.com> wrote in message
news:a0c501c43475$557426f0$a101280a@.phx.gbl...
> When i try to connect from remote computer to sequel
> server i get the followin message
> connection failed.
> i'm connecting using odbc, i'm new to this so all help
> thanks in advance.

Connection failed

Wednesday, March 7, 2012

Connection failed

connection failed

When i try to connect from remote computer to sequel
server i get the followin message
connection failed.
i'm connecting using odbc, i'm new to this so all help
thanks in advance.HI,
Create you create a Alias name for your sql server remote machine using the
"Client Network Utility" by providing
Protocol as TCP/IP, IP address of sql server machine and port number.
After this use this Alias name to connect to sql server machine.
Thanks
Hari
MCDBA
"mike" <anonymous@.discussions.microsoft.com> wrote in message
news:a0c501c43475$557426f0$a101280a@.phx.gbl...
> When i try to connect from remote computer to sequel
> server i get the followin message
> connection failed.
> i'm connecting using odbc, i'm new to this so all help
> thanks in advance.

connection failed

When i try to connect from remote computer to sequel
server i get the followin message
connection failed.
i'm connecting using odbc, i'm new to this so all help
thanks in advance.HI,
Create you create a Alias name for your sql server remote machine using the
"Client Network Utility" by providing
Protocol as TCP/IP, IP address of sql server machine and port number.
After this use this Alias name to connect to sql server machine.
Thanks
Hari
MCDBA
"mike" <anonymous@.discussions.microsoft.com> wrote in message
news:a0c501c43475$557426f0$a101280a@.phx.gbl...
> When i try to connect from remote computer to sequel
> server i get the followin message
> connection failed.
> i'm connecting using odbc, i'm new to this so all help
> thanks in advance.

Connection failed

Connection error to remote SQL instance, over VPN

I am trying to connect to an instance of SQL Express through a vpn, simply using the SQL Management Studio, providing the server ip address x.x.x.x\MSSQLSERVER, and using SQL authentication login. I receive the following message:

Cannot connect to <server>, etc., etc.

error 25: - Connection string is not valid

Does anyone understand this? I am trying to connect through the SQL Server Management interface, not with a client program that would utilize a connection string. Is there something which prevents Management Studio from working over a vpn?

To connect, I am using SQL authentication, and have verified the login and password locally on the target pc. The SQL browser service is running on the target pc, and I can telnet to the port which it is monitoring, through the same vpn connection. Remote connections are enabled for TCP/IP in the Surface Area configuration on the target pc.

Any help appreciated.

x.x.x.x\MSSQLSERVER is not correct. You cannot use MSSQLSERVER as the instance name because it is reserved for default instance. Since your instance is SSE, you should use x.x.x.x\sqlexpress. Based on your description, your connection should work with the fix. Please make sure UDP port 1434 (used by sql browser) is blocked by firewall.|||

SSE is installed as the default instance, so /MSSQLSERVER does work, as tested locally. Also the assigned port is opened through the firewall, as tested by telnetting through the vpn.

However here is additional information since I posted the problem: Using a packet tracker, I can see no handshaking messages are transmitted on the vpn network when the connection is attempted by SSE Studio. If I connect to a local SQL pc (on my local, non-virtual network), I see the TCP messages, handshaking, etc. and it instantly connects. Why does SSE Studio not attempt to connect over the vpn network? Ping and telnet do work over that network, so the operating system correctly distinguishes the networks. Just not SSE Studio. Is there a way to force it to this network?

|||If it's default instance, you should remove MSSQLSERVER, use x.x.x.x only. Also, use c:\windows\system32\cliconfg.exe on your client machine to check whether TCP is enabled on the client. Is your server listening on TCP port 1433? If not, please confirm sql browser is running and UDP port 1434 is in firewall's exception list. Thanks.|||

I figured it out, the connection text must specify the port after the ip address. Format:

x.x.x.x,1433 (or whatever port #)

It works in SSE Studio, and in the client app. (Access project). An example is here: http://www.connectionstrings.com/, under SQL Server connections -> SqlConnection(.NET) -> connection via ip address.

What is confusing is that the port specification is apparently not required if connecting to another pc on the same lan, only if connecting over the internet/vpn.

|||

If x.x.x.x,1433 workes, x.x.x.x should work unless your have any alias defined for x.x.x.x. You use c:\windows\system32\cliconfg.exe to check it.

If you tcp port is not 1433, then you must make sure sql browser is running and UDP port 1434 is not blocked. "x.x.x.x,port" can bypass the requirement of sql browser.

Saturday, February 25, 2012

connection error

I am getting following error while connecting in sql server. i have already disabled firewall, enabled remote connections using pipe and tcp and made sure the sql server and sql browser services are running.

but still the problem persists...can any help me ?

Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establi
shing a connection to the server. When connecting to SQL Server 2005, this failu
re may be caused by the fact that under the default settings SQL Server does not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.

thanks in advance

Do you have a named instacne or a default one ? how are you connecting, you will have to provide some more information on your situation to make it easier forus to give you the right suggestions.

Jens K. Suessmeyer

http://www.sqlserver2005.de

Sunday, February 19, 2012

Connection

Hello,
I don't know why i can not connect to a remote Sql server in my Enterprise
Manager, While i can do it through Query Analyzer.
ThanksHi
What is the error message you are getting?
Are you using the right account to connect?
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mathew" <Mathew@.discussions.microsoft.com> wrote in message
news:E05BE8E4-4937-47D1-A815-06278C45732B@.microsoft.com...
> Hello,
> I don't know why i can not connect to a remote Sql server in my Enterprise
> Manager, While i can do it through Query Analyzer.
> Thanks|||hello,
The error message is "Timeout Expired", that's it.
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> What is the error message you are getting?
> Are you using the right account to connect?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Mathew" <Mathew@.discussions.microsoft.com> wrote in message
> news:E05BE8E4-4937-47D1-A815-06278C45732B@.microsoft.com...
>
>|||The default login timeout in Enterprise Manager is 4 secs
and you probably need to increase that.
In Enterprise Manager, go up to the menu to Tools, select
Options. This opens the Enterprise Manager Properties
window. Click on the advanced tab and increase the login
timeout to something greater than the default 4 seconds.
-Sue
On Fri, 16 Dec 2005 12:56:03 -0800, Mathew
<Mathew@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>hello,
>The error message is "Timeout Expired", that's it.
>"Mike Epprecht (SQL MVP)" wrote:
>

Connection

Hello,
I don't know why i can not connect to a remote Sql server in my Enterprise
Manager, While i can do it through Query Analyzer.
Thanks
Hi
What is the error message you are getting?
Are you using the right account to connect?
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mathew" <Mathew@.discussions.microsoft.com> wrote in message
news:E05BE8E4-4937-47D1-A815-06278C45732B@.microsoft.com...
> Hello,
> I don't know why i can not connect to a remote Sql server in my Enterprise
> Manager, While i can do it through Query Analyzer.
> Thanks
|||hello,
The error message is "Timeout Expired", that's it.
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> What is the error message you are getting?
> Are you using the right account to connect?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Mathew" <Mathew@.discussions.microsoft.com> wrote in message
> news:E05BE8E4-4937-47D1-A815-06278C45732B@.microsoft.com...
>
>
|||The default login timeout in Enterprise Manager is 4 secs
and you probably need to increase that.
In Enterprise Manager, go up to the menu to Tools, select
Options. This opens the Enterprise Manager Properties
window. Click on the advanced tab and increase the login
timeout to something greater than the default 4 seconds.
-Sue
On Fri, 16 Dec 2005 12:56:03 -0800, Mathew
<Mathew@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>hello,
>The error message is "Timeout Expired", that's it.
>"Mike Epprecht (SQL MVP)" wrote:

Friday, February 17, 2012

Connectio to Remote SQL Server from another SQL Server Stored Proc

Hi,
I have a problem with a conection to Remote SQL Server Database wich have a
blank space in databese name.
Ex.
"Production ED"
I Can`t change the name of this data base.
I Need to connect this database with a Stored Procedure in another Server.
Both Databases are SQL Server 2000 Ent. Ed.
Would it help if you put the name in brackets?
[Production ED]
so you could do something like...
select * from
[Production ED].dbo.ProcedureName
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Esteban" <Esteban@.discussions.microsoft.com> wrote in message
news:7CA8D942-0B44-434C-BD4D-34E4231DC7E8@.microsoft.com...
> Hi,
> I have a problem with a conection to Remote SQL Server Database wich have
> a
> blank space in databese name.
> Ex.
> "Production ED"
> I Can`t change the name of this data base.
> I Need to connect this database with a Stored Procedure in another Server.
> Both Databases are SQL Server 2000 Ent. Ed.

Tuesday, March 27, 2012

connection problem

connection problem

Sunday, March 25, 2012

connection problem

Thursday, March 22, 2012

Connection over Internet

Connection over Internet

Sunday, March 11, 2012

Connection from PHP slower when server is remote

Connection from PHP slower when server is remote

Connection from PHP slower when server is remote

Thursday, March 8, 2012

connection failed - ODBC from remote SQL SERVER

connection failed

Connection failed

Wednesday, March 7, 2012

Connection failed

connection failed

connection failed

Connection failed

Connection error to remote SQL instance, over VPN

Saturday, February 25, 2012

connection error

Sunday, February 19, 2012

Connection

Connection

Friday, February 17, 2012

Connectio to Remote SQL Server from another SQL Server Stored Proc

asp sql server

Blog Archive

About Me