CODEWITHSUNDEEP
asp.netsql-server-2005
Ducain
Ducain

Reputation: 1591

What is the best way to address the local server in a SQL connection string for ASP.net?

We have a 2K3 server we're using as both a database server AND a web server - fairly small traffic website. I know, should be 2 separate servers, but isn't going to happen soon.

Currently, we have 2 NIC cards on this server, and in-house workers use custom apps that hit NIC1 all day long. We also have the connection string for the website using that same IP address.

I'm wondering if it would benefit us at all to use the IP for NIC2 for the connection string for the website SQL, or if would be a waste of time.

Also, I'm wondering in a setup like this, where the SQL server IS the local server, is there a better way to address the server in the connection string than using the IP?

I'm simply trying to maximize the network we have and not create any bottlenecks.

Thanks much.

Upvotes: 1

Views: 510

Answers (3)

Xenon
Xenon

Reputation: 815

I always use "." for local but sometimes it rejects in some servers (local) is working for all servers.

Upvotes: 0

blowdart
blowdart

Reputation: 56530

If you use (local) as the server name that will default to using Named Pipes, which, on the same machine, has less overhead than the TCP/IP stack.

Upvotes: 4

Ed Manet
Ed Manet

Reputation: 3178

I would use localhost. It will resolve faster than fully qualified domain name.

Upvotes: 0

Related Questions