Re: Shared Memory from older app SQL Server 2005
- From: "djouungk@xxxxxxxxxxx" <djouungk@xxxxxxxxxxx>
- Date: Mon, 13 Aug 2007 13:19:54 -0700
Well, I can tell you from previous experience that it is sending query
after query at the engine whether it needs it or not.
The programming for this thing is awful. One process that used to
take 16 hours, I was able to profile and see what they were doing. I
redid it in MS Access and it runs in under 2 minutes ... ON THE SAME
MACHINE.
So, what I'm probably going to have to do is write our own version of
these utilities using .NET and solve this issue once and for all.
Thanks for the help!
.
- 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
- Re: Shared Memory from older app SQL Server 2005
- From: djouungk@xxxxxxxxxxx
- 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: Cannot login to SQL Server 2005 using SQL Server Authentication
- Next by Date: Re: Linked server strangeness in SQL 2005 Mgmt Studio
- 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):
Loading