James
Thu Nov 06 14:38:06 CST 2003
Oh, yes, web dav calls are extremely slow. I wouldn't run a web app that
access SPS (2001) on a machine other than the SPS machine itself. You
could, I guess write a web service to get your SPS data on the local machine
(the same way you did with your old application which was installed locally)
and send it to the application on the new system, but I am not sure that you
get you much additional speed.
--
James Edelen
Microsoft MVP - SharePoint Portal Server
Microsoft MVP - Windows XP Media Center
Microsoft Associate Expert
Expert Zone -
http://www.microsoft.com/windowsxp/expertzone
"Jason S" <someone@somewhere.com> wrote in message
news:OD1FVQKpDHA.2000@TK2MSFTNGP10.phx.gbl...
> What I have is a web app that has sps 2001 installed locally that is being
> migrated to a newer ver of windows. I was hoping the sps server could
stay
> where it is and I could continue to make webdav calls into it from the
newer
> system thus easing the migration process.
>
> Problem is... it is extremely slow.
>
> If I can make this any clearer let me know.
>
> Thanks,
> Jason
>
> "James Edelen [MVP]" <jj4@mvps.org> wrote in message
> news:elgopCKpDHA.3612@TK2MSFTNGP11.phx.gbl...
> > I am not sure I really understand what you are doing. Are you trying to
> > proxy webdav calls through the SPS 2003 server (don't see that as being
a
> > good idea at all). I would recommend if you are sure you want to keep
the
> > older SPS 2001 system, just provide links to it with your new system.
> There
> > is not really good way to "integrate" them. This way the portal
> performacne
> > should be as good as it was previously (before SPS 2003)
> >
> > --
> > James Edelen
> > Microsoft MVP - SharePoint Portal Server
> > Microsoft MVP - Windows XP Media Center
> > Microsoft Associate Expert
> > Expert Zone -
http://www.microsoft.com/windowsxp/expertzone
> > "Jason S" <someone@somewhere.com> wrote in message
> > news:uia1NmJpDHA.1020@TK2MSFTNGP09.phx.gbl...
> > > James,
> > >
> > > First, thanks for your response. The upgrade path may indeed be a
valid
> > > choice for things moving forward but at this point we want to look at
> the
> > > option of leaving the sharepoint stuff on the older server. We have a
> lot
> > > of code in our hand rolled portal site that accesses the sps 2001.
From
> > > what I understand this is not backward compatible unless you run in
the
> > > older mode.
> > >
> > > Here's the deal... when I analyze performance on a box that has sps
> > > installed locally I get great numbers, when it is remote and the calls
> are
> > > being made from the local web server to a NON-LOCAL store it is
> absolutely
> > > terrible.
> > >
> > > Is there anything I can do to alleviate this?
> > >
> > > Regards,
> > > Jason
> > >
> > > "James Edelen [MVP]" <jj4@mvps.org> wrote in message
> > > news:OrYq0FJpDHA.2772@TK2MSFTNGP10.phx.gbl...
> > > > Why didn't you upgrade from SPS 2001 to 2003? There is a supported
> > valid
> > > > upgrade path. Also note that SPS 2001 (and the backward compatible
> > > > libraries for 2003) don't scale exceptionally well, so you ,may want
> to
> > > > prepare a migration path from the Web store to Sql libraries.
> > > >
> > > > --
> > > > James Edelen
> > > > Microsoft MVP - SharePoint Portal Server
> > > > Microsoft MVP - Windows XP Media Center
> > > > Microsoft Associate Expert
> > > > Expert Zone -
http://www.microsoft.com/windowsxp/expertzone
> > > > "Jason S" <someone@somewhere.com> wrote in message
> > > > news:#iF3q2IpDHA.2612@TK2MSFTNGP10.phx.gbl...
> > > > > Hello group,
> > > > >
> > > > > I have a situation where I am trying to migrate a site off of a
> > windows
> > > > 2000
> > > > > server with sharepoint portal server 2001 to a small web farm
> running
> > > > > windows server 2003. Now, obviously sps 2001 doesn't run on
win2003
> > so
> > > > the
> > > > > solution thus far has been to keep the sps portion on the old
server
> > and
> > > > > just make the calls from the farm servers to the old server. This
> is
> > > > > extremely slow... in fact when running a load to perf test the new
> > farm
> > > > > anything that has a sharepoint call (webdav call) really really
> lags.
> > > > After
> > > > > a few calls from the farm the sharepoint server stops
responding...
> no
> > > > > errors or bad perf on the sps server... just no response... like
the
> > > > > response got lost.
> > > > >
> > > > > I have isolated this to the webdav calls... other database and
plain
> > > aspx
> > > > > pages work just fine... so it's not a network problem insofar as I
> can
> > > > tell.
> > > > >
> > > > > Any insight is appreciated.
> > > > >
> > > > > Regards,
> > > > > Jason
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>