Re: Shared Memory from older app SQL Server 2005



It would help to know if the application uses ADO, DAO or ADO.NET to access SQL Server.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

<djouungk@xxxxxxxxxxx> wrote in message news:1186883283.734610.146740@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
We have an application that we run at our business that takes a long
time to run on our old server. We purchased a new server and I have
been told we are going to run SQL Server 2005 STD x64. When I ran the
program as a test on our new server it took twice as long as the older
slower server.

What I've determined is that we used to connect to SQL Server 2000 via
Shared Memory, but now cannot. It only allows named pipes and tcp/
ip. I think I read somewhere that MDAC does not support the SQL
Server 2005 version of Shared Memory protocol.

When I tested this server using SQL Server 2000, our program ran in
1/3 of the time on the new server, which is what we were hoping. I
still have to use SQL Server 2005 though and hope to come up with some
kind of solution.

Any advice would be appreciated,
Thanks,
Doug


.



Relevant Pages

  • Re: What are OleDbParameter names with Original_ prefix?
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ... Since the table has a primary key column, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: ADO.NET Transaction
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ... Client transactions put too much schema-dependent, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Performance problems with OracleDataReader
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ... referencing the columns by ordinal is far faster than using strings. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Very slow
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ...
    (microsoft.public.sqlserver.ce)
  • Re: ADO.NET Transaction
    ... The SqlBulkCopy class can take anything you can expose with a DataReader and send it to SQL Server in a single high-speed operation. ... Hitchhiker's Guide to Visual Studio and SQL Server ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ... Client transactions put too much schema-dependent, ...
    (microsoft.public.dotnet.framework.adonet)

Loading