A war between me and the network admin over the SQL EXPRESS

The network admin is saying that if I run my SQL Express in the office , it will intefere with his SQL Server 2000 connection and its services.

He asked me to disconnect myself from the network and do the work locally, what the!?

I had my SQL express remote connection set to Local and remote connections (using TCP/IP connection )

However , I really dont believe a SQL express running on my laptop would in anyway steal incoming connection to the SQL server 2000 running on the company server.

I now have my SQL express set to Local connections only, I would like to ask you guys does SQL express actually conflict with ANY services running on the same network ?
Thanks a million

No actually not. The service is a server based network service, in the meaning that you wil lhave to adress the server or any virtual device in a cluster environment to establish a connection to the service. SQL Server does not "steal" anything.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

Here is more detail:

The company runs a Window Server 2003 and SQL Server 2000 and exchange server. The SQL server has reporting service and some other "advanced features" available to other interstate's branch network.

My laptop has a SQL Express installed, and the SQL express is set to Local and TCP/IP connection. My laptop has ethernet connection to the company network for internet access. The domain of my laptop is "AAA" and it is used by the software division only (no one else within the same domain is running SQL express).

The admin is complaining about the MSSQLEXPRESS from my SQL Express is somehow affecting the server. How this could affect the win server 2003 in anyway? As Jens say the SQL Express is a server based network service, what I think is, unless you attempt to set your win server to bypass incoming SQL request to my laptop IP address which has a SQL Express running, otherwise my SQL express should not be able to steal or disturb other services running on different IP.

I would like to see anyone who has this problem before?

Thanks

|||

Hi again,

to clarify: Compared to a telephone net, your telephone is called on a specific number. There is no chance that another telephone will ring and will be ansered if the caller dialed the right number. The telephone won′t force to aquire the incoming call. This is just a point2point connection.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Thanks Jens, me and my supervisor also think the SQL server express is a server and the nature of a server is to sit there listenining for incoming connection and serve data on request. Yeah, there is no point the server application is playing up because someone runs a SQL express on different IP address on different domain, different IP.

We don't know what got into the network admin but what is certain is we will try to avoid this guy as much as possible.

A transport-level error has occurred when sending the request to the server

Hi all,

I am new to SQL 2005. I have one issue and it is as follows:

I write a simple query and run it; it works fine.

Now I break the network connection and run the query; in this case it runs fine.

But when I reconnect the network and run the query, then I get an error as follows:

"A transport-level error has occurred when sending the request to the server. (provider: Named Pipes Provider, error: 0 - An unexpected network error occurred.) "

Every thing is local here. So how the network issue comes here?

For some reason the connection was made through Named Pipes instead of Shared Memory (the default for local connections), which suggests that SqlClient did not recognize the connection was local, and most likely tunneled Named Pipes over TCP, hence, disocnnecting the network has impact.

How do you specify the server name - perhaps by its fully qualified domain name (FQDN), or IP address?

If you specify it by the hostname or "." or "(local)" SqlClient should recognize the local connection, and you should not see the error.

|||

Hi ,

sorry to reply late.

I tried the above mentioned case. In case of "." or "(local)" it did not connect to the SQL server. When I try it by the host name then same original problem persist.

Thanks

|||

Well sorry once again!!!

I made some mistake in the above reply.

I tried as mentioned in the solution and here are the results:

In case of "." it works fine

In case of host name the problem still persists.

for "(local)" I have not yet tested.

Thanks

|||

Regarding the host name problem - do you specify the server name exactly the same way as returned by the Windows hostname command-line command?

|||

Yes, I specify the server name exactly as returned by the the windows hostname command-line command. But the problem still persists.

|||

Great post ~ I had the same problem.

When trying to connect to a local SQL Server I was using 'localhost', which resulted in "A transport-level error has occurred...".

To resolve, I replaced 'localhost' with '(local)', as suggested.

Regards.

|||I same the same problem but I am connecting to remote server using IP, any idea?

A transport-level error has occurred when sending the request to the server

Hi all,

I am new to SQL 2005. I have one issue and it is as follows:

I write a simple query and run it; it works fine.

Now I break the network connection and run the query; in this case it runs fine.

But when I reconnect the network and run the query, then I get an error as follows:

"A transport-level error has occurred when sending the request to the server. (provider: Named Pipes Provider, error: 0 - An unexpected network error occurred.) "

Every thing is local here. So how the network issue comes here?

For some reason the connection was made through Named Pipes instead of Shared Memory (the default for local connections), which suggests that SqlClient did not recognize the connection was local, and most likely tunneled Named Pipes over TCP, hence, disocnnecting the network has impact.

How do you specify the server name - perhaps by its fully qualified domain name (FQDN), or IP address?

If you specify it by the hostname or "." or "(local)" SqlClient should recognize the local connection, and you should not see the error.

|||

Hi ,

sorry to reply late.

I tried the above mentioned case. In case of "." or "(local)" it did not connect to the SQL server. When I try it by the host name then same original problem persist.

Thanks

|||

Well sorry once again!!!

I made some mistake in the above reply.

I tried as mentioned in the solution and here are the results:

In case of "." it works fine

In case of host name the problem still persists.

for "(local)" I have not yet tested.

Thanks

|||

Regarding the host name problem - do you specify the server name exactly the same way as returned by the Windows hostname command-line command?

|||

Yes, I specify the server name exactly as returned by the the windows hostname command-line command. But the problem still persists.

|||

Great post ~ I had the same problem.

When trying to connect to a local SQL Server I was using 'localhost', which resulted in "A transport-level error has occurred...".

To resolve, I replaced 'localhost' with '(local)', as suggested.

Regards.

|||I same the same problem but I am connecting to remote server using IP, any idea?

a server hardware/environment question..

my network admin gives me two servers to set up for sql2k.
one will be for dev/testing qa, and one will be for production (mostly
reporting , not business operation type of stuff)
one server is good (raid 5), and the other is very good (raid 10).
the type of development will be in VB and data warehousing areas with
about 5 developers. the audience for the production reports can range
from a few people to a couple of hundreds of employees.
what would make the most sense in terms of server allocation?
should i give the best server to dev/testing? or to production (mainly
for reports)?
thank you.I tend to always give production the edge when building a dev server
(if I ca't have identical boxes); it will be more likely that
performance issues will show up on the weakest server, and I would
prefer to deal with them during development rather than production.
What would make this question interesting would be the processor and
memory specs as opposed to just the hard drive allocations...
HTH,
Stu|||On the development server when designing queries and report design
templates, you will probably want to work with more manageable subsets of
data, so the lessor equipped server should suffice. My development server is
typically just my PC with a local intall of SQL Server Developer edition.
"=== Steve L ===" <steve.lin@.powells.com> wrote in message
news:1121891806.861200.159450@.g49g2000cwa.googlegroups.com...
> my network admin gives me two servers to set up for sql2k.
> one will be for dev/testing qa, and one will be for production (mostly
> reporting , not business operation type of stuff)
> one server is good (raid 5), and the other is very good (raid 10).
> the type of development will be in VB and data warehousing areas with
> about 5 developers. the audience for the production reports can range
> from a few people to a couple of hundreds of employees.
> what would make the most sense in terms of server allocation?
> should i give the best server to dev/testing? or to production (mainly
> for reports)?
> thank you.
>|||> What would make this question interesting would be the processor and
> memory specs as opposed to just the hard drive allocations...
Yes, definitely if you can, have more than one processor in dev if your
production machines have > 1.
(Often problems due to parallel processing / plans can be missed because the
first time the queries have a chance to utilize that hardware is in
production.)
Also, try to have the same amount of memory, e.g. if production uses AWE
then you should have the same settings in dev (for the same reasons as
above).

A problem to connect to sql server 2000

The sql server 2000 is runing at network pc named: pc1;
The ado.net is used to access the server with OLE DB .net
data provider.
The error at the OleDbError is
Message: SQL Server does not exist or access denied
NativeError: 17,
SQLState: 08001
Below is potion of the code (in C#):
OleDbConnection connection = null;
string cnString = @."Provider=SQLOLEDB; Data Source=\\pc1;"
+ "Initial Catalog = BOM; User ID = pyoung;
Password=pyoung";
try
{
connection = OleDbConnection(cnString);
connection.Open();
}
catch
{
for (int i=0; i < myException.Errors.Count; i++)
{
this.mStatusMsg = "Message: " + myException.Errors
[i].Message + "\\n" +
"Native: " + myException.Errors
[i].NativeError.ToString() + "\\n" +
"Source: " + myException.Errors[i].Source + "\\n" +
"SQL: " + myException.Errors[i].SQLState + "\\n";
}
connection.Close();
}
Where BOM is the database to use.
What did I miss to connect to the server correctly?
Thanks.
Pat
Data Source in your string is wrong.
Provider=SQLOLEDB.1;Persist Security Info=False;User ID=useridHere;Data
Source=ServerNameHere
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||You are right. So the Data Source is only the name
instead the path.
Thank you very much.
Pat
>--Original Message--
>Data Source in your string is wrong.
>Provider=SQLOLEDB.1;Persist Security Info=False;User
ID=useridHere;Data
>Source=ServerNameHere
>
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>
|||You're welcome!
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

A problem to connect to sql server 2000

The sql server 2000 is runing at network pc named: pc1;
The ado.net is used to access the server with OLE DB .net
data provider.
The error at the OleDbError is
Message: SQL Server does not exist or access denied
NativeError: 17,
SQLState: 08001
Below is potion of the code (in C#):
OleDbConnection connection = null;
string cnString = @."Provider=SQLOLEDB; Data Source=\\pc1;"
+ "Initial Catalog = BOM; User ID = pyoung;
Password=pyoung";
try
{
connection = OleDbConnection(cnString);
connection.Open();
}
catch
{
for (int i=0; i < myException.Errors.Count; i++)
{
this.mStatusMsg = "Message: " + myException.Errors
[i].Message + "\\n" +
"Native: " + myException.Errors
[i].NativeError.ToString() + "\\n" +
"Source: " + myException.Errors[i].Source + "\\n" +
"SQL: " + myException.Errors[i].SQLState + "\\n";
}
connection.Close();
}
Where BOM is the database to use.
What did I miss to connect to the server correctly?
Thanks.
PatData Source in your string is wrong.
Provider=SQLOLEDB.1;Persist Security Info=False;User ID=useridHere;Data
Source=ServerNameHere
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||You are right. So the Data Source is only the name
instead the path.
Thank you very much.
Pat
>--Original Message--
>Data Source in your string is wrong.
>Provider=SQLOLEDB.1;Persist Security Info=False;User
ID=useridHere;Data
>Source=ServerNameHere
>
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>|||You're welcome!
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.