Re: Shared Memory from older app SQL Server 2005
- From: "djouungk@xxxxxxxxxxx" <djouungk@xxxxxxxxxxx>
- Date: Sun, 12 Aug 2007 19:23:24 -0700
On Aug 12, 5:25 pm, "William Vaughn" <billvaNoS...@xxxxxxxxx> wrote:
Okay, that means it's COM-based ADO which does not need to use MDAC to
access SQL Server--the app can be changed to use the SQL Server
2005-specific OLE DB "SNAC" provider (which has no MDAC dependency). Look
for "SQL Server Native Client" on the MS site. Simply changing the
ConnectString should help. I expect that it does have a shared memory
interface when accessing SQL Server locally, but this assumes that the
ConnectionString does NOT force ADO to look up the server name in the DNS
over the network. That is, it must have "." or "(local)" as the server
name--not the actual name.
Well, this program is a purchased program so I have no idea if it's
being forced or not. It was written in some SQL language and
compiled. It's really awful. I changed the config file to read both
"." and "(local)" and it still is connecting via named pipes. I guess
i'm out of luck on this point.
All that said, consider that SQL Server is no better at making an
application that's not written correctly work any better. It also cannot
make up for the fact that the newly installed database has not been properly
configured, does not have indexes, has not had the statistics updated, or
the server does not have enough (dedicated) RAM and CPU time or a long list
of other issues. Is the server being shared with other services like a print
spooler, Reporting Services or Analysis Services? Are there other
applications running on the server that compete with SQL Server?
Like I said, it is a horribly written program. We have a Quad core
2.66 GHz CPU with 16GB of ram. We are using Windows 2003 x64 R2
Enterprise with SQL 2005 x64 Std. (Test box atm, SQL Server is all
that's installed)
When I use SQL Server 2000 with Windows 2003 R2 (both 32 bit) the
process takes around 3.5 hours for one test and 11 hours for a
different test. When I run it with the Enterprise/2005 it takes
around 6 hours with named pipes and 8 hours with TCP/IP, while the
other test runs 20 hours on the named pipes with SQL 2005, and 29
hours with TCP/IP on SQL 2005. We'd like to be able to run this
process overnight, but I don't think I will be able to if I'm pigeon
holed into using SQL 2005.
.
- Follow-Ups:
- Re: Shared Memory from older app SQL Server 2005
- From: William Vaughn
- Re: Shared Memory from older app SQL Server 2005
- References:
- Shared Memory from older app SQL Server 2005
- From: djouungk
- Re: Shared Memory from older app SQL Server 2005
- From: William Vaughn
- Re: Shared Memory from older app SQL Server 2005
- From: djouungk@xxxxxxxxxxx
- Re: Shared Memory from older app SQL Server 2005
- From: William Vaughn
- Shared Memory from older app SQL Server 2005
- Prev by Date: Re: Can't Connect
- Next by Date: RE: How to connect test to production system
- Previous by thread: Re: Shared Memory from older app SQL Server 2005
- Next by thread: Re: Shared Memory from older app SQL Server 2005
- Index(es):
Relevant Pages
|
