subject: RE: Outsourcing spooled file and a little .NET rant

Walden,
Thanks for taking the time to respond.

Transfer speed: I don't think it was on the 400 side. From what I
remember, we got a third party driver (Hit?) that was better than the
original attempt. But, it still lacked the speed we expected.

PC Crash: Within the last month, we spent three weeks in our training
room remoted into our new laptops. You might have something there - I
don't think the training room desktops were the latest and greatest. It
was always a VS2005 error. I'd guess it was always when I was in debug
mode. I just hit F5 to run - it's easier than a mouse click - so I am
mostly in debug mode whether I am debugging or not.

Large Volumes of data: I'll have to check with my cohorts to see just
exactly what we were asking it to do. We had a consultant in for those
three weeks  for questions and impromptu short classes. She worked along
with us and we just harrassed her constantly with questions. It was an
excellent session. She did some programming and answered and answered
and answered. During one of those days, we were asking the large volume
of data question. We thought we were OK - just checking with her. I'll
recharge my memory next week. I'd surely like to get your take on this.

Thanks again,
Fran D


------------------------------

message: 6
date: Fri, 29 Dec 2006 15:35:09 -0500
from: "Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>
subject: RE: Outsourcing spooled file and a little .NET rant

Well, we tried option one at first and found that it took too long to

transfer data. 

It is not an option anymore - we just need the speed. So, here we are

developing 

everything in Visual Studio 2005 with the data in SQL Server. 

Strange -- something was wrong. The iSeries makes a very nice database
server, should have worked fine.

Our PCs seldom crashed until we as developers started using Visual

Studio 2005.

PC specs? Modern machine? We have many developers running VS.Net 2005
all day long w/out crashes -- heck, we don't reboot at all unless
forced
by a patch, maybe once a month? (Yes, I mean desktops)

We ran into a couple of issues with large volumes of data right now

in
development.

Care to elaborate? Do you have a properly sized machine, or are you
"in
development" on a desktop pc w/one SATA drive? We regularly use S2K
and
S2K5 w/datasets well over 1M rows and achieve sub-second response
times.